I believe this feature would greatly increase the usability of Construct 2 IDE.

Basically, a search feature that searches for all events using the search term, which can be an object, a variable name or a string.

As a result, all matching actions and conditions are highlighted.

Example: troubleshooting a project. Lives are bugged, don't behave as expected. I search for the variable "Lives" and all actions/conditions containing the variable are highlighted. This makes locating the bug much easier.

Another example: Say I am removing some object from the object, however quite a few events are dependent on it. I have to adjust those manually, but the project had gotten larger since then and it is difficult to find all references of the object. I would search for the object uses and all matching actions or conditions would be highlighted.

Strange! The OP seems to have deleted his post, I was responding to him, I did not start this thread!

Tom, you may want to investigate this.

Whenever you play a sound, you have an option to set the tag.

Then, when you stop a sound, you can stop by tag.

In pseudocode kind of:

for i = 0 to 8 do

array[i%3,floor(i/3)] = i+1

Something like that, off tip of my mind.

Actually, even simpler, in the for every element loop, just set the current value to x*y. If zero indexed... (x+1)*(y+1)

If Javascript is the assembly of the web, then we'll code in assembly.

<img src="http://lh3.ggpht.com/haymansbeard/RrFkGaI8atI/AAAAAAAAAJI/NUu4EF66oy8/King+Leonidas+Large.JPG" border="0" />

Couldn't resist... :(

Well, I use strings for finite state machine, booleans for dual states (on/off and toggles) and numbers for mathy stuff as well as enumeration.

I would be ecstatic with an array as a variable (for example ["PowerAttack",2,true]), but well, I guess that's still far fetched right now!

Place all collidable objects in a family, then check for collision of that family with the specific object and finally destroy the family member.

OH HELL NO!

It makes troubleshooting a PAIN. Readable code goes much further than "optimized" code.

Or you could make use of blend mode. Drop outline sprites onto a separate layer that's under character layer and set blend to... eh, don't remember what, just experiment with it.

I often use string variables, while less efficient than numbers and booleans, they're much more readable and the difference is really negligible. Variables aren't no bottlenecks and won't be for decades to come, unless you use some weird code such as huge nested loops.

Looking good!

You may want to fix your signature, though, the URL is wrong.