No reason that shouldn't work. You'd have to show more.
You do a subsequent pick: Pick nth instance (pick 0).
That's different code though - not what have here. Presumably the condition would stop quickly and the While will exit. The test code doesn't meet this requirement.
Develop games in your browser. Powerful, performant & highly capable.
http://www.blackhornettechnologies.com/Construct2Stuff/FadeLayer.capx
First, you can't bury your fade inside the touch. That code is executed just once on the tap. Don't mix the layer names and numbers. That might be another problem.
C2 is already a giant While loop, So you don't need while at all. get rid of it and add an Else to the event for the NOT case.
You have to decrease the opacity value over time. How are you doing that? Typically done Every tick until you reach 0.
—
You'd have to do them yourself, at that size.
This thread is out of date. C2 exports the correct external plugin, and you just need to call:
Browser -> Execute Javascript = "StatusBar.hide();"
There are various threads on this.
You need to convert from your Player layer to the Canvas, then from the Canvas to the BG layer.
http://www.blackhornettechnologies.com/Construct2Stuff/EnemysDestroyedOnParallaxLayer_BHT.capx
C2 always runs in order. It's Wait that runs things out of order. You should be fine.
You should always set your groups activation on startup.
You need to reset things on Start of layout. Groups hold their state by design. Reset your bullets also.
Member since 28 May, 2012