So Rich,
in base we agree.
Picking objects is easy. You brought them by urself in the scene. You can see there Unique ID's.
You can work on theire names.
Instances created on runtime are not that easy to pick.
Theirfor, its very importand that events (combined with a condition) that pick an instance of an object pass their information the righ way to the actions.
I assume we agree on that too.
If the events are not able to do that, any fancy shader, any beautyfull made behaviour, any system object has no use.
Its like delevering a car with no steer and wheels.
I asked for an event "for each object on layer (x)' to simplyfie the picking of instances created on the run.
Half of that is allready in place beacuse u can create instances on layer (x), and that works perfect too.
Layers are a perfect and visual way to determinate groeps of objects at run tme, even better then the use of familys.
now with the event "for each object" combined with a condition " and how its implemented i have 2 problems.
One is general. Meaning, shifting this in 2 lines of code is confusing and it is the finger on the little shortcoming that hurts the whole events editor. It is a loop too, and not an event. Conditions paired to a loop should be placed in the actions. Why it should be 1 line of code.
De combination of 2 lines generates a lot of hidden errors too. (not bugs) Because the event editor allows u at present time to combine everything and anything, with no steering error reporting.
Let me return on this later on.
The second problem i have with that construction is specific to this construction. Namely, i was suggested to try "for each object" comebined with "is on layer". I ofcourse tried that and uploaded the . cap. So u guys could correct me if i am wrong. Its the link that made ashley upset. De construction dont work, less i put it wrong. So far no one made any attempt to look at the .cap.
And this again is a general pain in the events editor. Loops dont seem to work a lot. The essential "else" dont work too.
To say it again "If the events are not able to do that, any fancy shader, any beautyfull made behaviour, any system object has no use."
Allright, the DVD of my program is written, means my time is up, back to work. At home i will return to what i promissed to return to.
The plain Jerk salutes you.
And i am still curious about any upshowing .cap holding a working tetris clone. And a reasonable dude/dudette who points out the problems he/she meets, so they get solved. Secondly, i hope this .cap will add to a the documentation for newbys to construct .
Thats our job btw, Ashley cant do all this, Ashley has to get his mind in the events editor.