Hi, after reading all of your replies and especially the one coming from Ashley. I think that construct2 has the potential to become the BEST html5 engine, code or no code, it just need to open up to its full potential.
I don't want to rely on firebug because then I would get a trace of the inner workings of construct, not of my "code" if I have to delve deeply in the recess of construct2 code I'm better off learning to code in a "real" html5 framework. At this point I would really settle off for a console.log(allmyvars);.
All the discussion on UID kinda make my point more valid. It's imperative to be able to access an object clearly after it has instanced, I don't care if UID changes, that is normal, what is not normal is that currently is a hit/miss thing.
There should also be a more clear way of understanding the flow and precedence of construct, I have often to rely on instancing an insane amount of variable like object_position_X,object_position_X1,object_position_X2, etc because sometimes var are overridden during complex instruction in an unpredictable way. This could be achieved simply by having groups behave like real functions, like
start group (passing variables)
do what the group does
deactivate the group automatically
Right now is kinda possible to do this, but it involves a check (is group active) and a consequent manual deactivation after the group does it's thing and when you have 10-20 groups it gets confusing and unpredictable.
Take a look at this: http://dl.dropbox.com/u/23551572/C2/destroyByUID.capx
(from this thread: http://www.scirra.com/forum/topic46461.html).
After working on this for several days (to expand my game) I found out that the whole isSelected bit is not completely reliable, I added tons of new event inside that bit and I started noticing a delay between the destroying of the first and second card, I presume because sometimes it misses the isSelected bit, goes back to the beginning and starts over, resulting in a bit of delay, this is a big issue because we have no instruments to check the precedence of instruction and the flow of construct.
Since I bought this product I've seen only updates that add even more "click and play" features (like jump through platform) and none that addresses the real issues, and I fear that if this is the road you are taking serious projects will never see the light of the day.