The ones that can't be inverted are triggers and many system events. Stuff like key pressed, collision with, functions, ... . Also loops and some other stuff where it wouldn't make sense.

after quite some testing, I found the problem. Seems to be some sort of computational error

use

Function.Param(0)+round(cos(loopindex("boomSides")*90))*loopindex("boomRange")

and

Function.Param(1)+round(sin(loopindex("boomSides")*90))*loopindex("boomRange")

when comparing the value in the array

sprite.imagepointx(1) and sprite.imagepointy(1)

1 being the index of the image point, so sprite.imagepointx(0) will give back sprite.x

I already wrote the correct code:

on any touch start AND is touching log object (inverted): do stuff

I mostly operate via mouth to mouth propaganda. I think it happens for a lot of people, that's why the really popular titles outsell the good but not as popular games by a big margin.

Example: DotA - only a custom map for Warcraft III, not marketed at all (in fact not even sold as a product), had a playerbase of around 15 million players in 2010.

Ofc there are also the big AAA titles with heavy marketing budget that get so much attention that people either assume they are good or at least can talk about them with friends, because they also play them.

<img src="http://666kb.com/i/cjgdzedtkjeqqgqii.png" border="0" />

this is just a basic implementation. Ofc you can make texts clickable, save the current array position they represent in a instance variable to easily detect which item each box represents, implement a scroll bar, create highlights, adjust/improve the controls for it, ...

Not sure what you mean with that. The code already does that, no? The slider is not a necessity.

Construct has the ability to invert conditions (rightclick on it -> invert).

So: on touch start, is touching log object (inverted) should do the trick

Since it is not possible to control the cycleposition, you should manually code the change of angles instead of using the sine behavior.

A slider maybe.

scirra.com/forum/random-frame-uniqe_topic80520.html

this is a better way to do it as you directly input what you want instead of looping till you find something what you want.

If you had 26 objects that need to be filled with a letter, the while loop for the last element could run quite a lot of times.

Link to .capx file (required!):

capx

Steps to reproduce:

1. on start of layout -> system create an object in a subevent

2. in other subevent -> pick all object: do something with the object

Observed result:

object that got created in the same event is not picked / accessible for further actions (when moving to another subevent branch)

Expected result:

object is able to be picked, because it was created in a subevent before this

Browsers affected:

Chrome: yes

Firefox: (don't know, probably yes)

Internet Explorer: (don't know, probably yes)

Opera: yes

Operating system & service pack:

Win 7 64bit SP1

Construct 2 version:

r147 beta, but also happens with r146