i would expect that a function in subevent would keep the selected object
in this example both objects are deleted instead of the one clicked on
(purely as simple example)
https://dl.dropbox.com/u/61666915/functioncall.capx
i just realise that no matter what, no picked objects are passed thru function, is this wanted? in classic you could keep picked objects...
like when you have a collision with an object you can pass this object to the function
Develop games in your browser. Powerful, performant & highly capable.
It's not supposed to. It was one of the bugs fixed in r110 :)
Bug Fix Function: in some cases the called function would still reference objects picked from the event calling the function. This was not intended; now function events start picking instances from scratch again.
Bug Fix
Function: in some cases the called function would still reference objects picked from the event calling the function. This was not intended; now function events start picking instances from scratch again.
That's the expected behavior.
If you want to emulate sol selection use the pick nth, or pick by uid conditions using the parameters of the function call.
Also we have on created, and destroyed triggers that do remember picked...
Just so you know.
Closing since this is currently by design - functions do not use the SOL from the calling event.