[Bug] String Objects outside visible area not destroyed

[JoKa]

This is not only related to the iOS runtime, but seems it came with the exporter's Beta 5. Is it ok to post it here?

I have multiple instances of a string. Events like
XPos(String)>500 ---> Destroy

don't work anymore. Works fine with Actives, but not with String Objects. (Inactivate if too far from window=NO)

[paobrasil]

I had this problem with active on beta5...but seen to be fine now on beta6...

[Francois]

Can you provide and example MFA? Thanks...

[JoKa]

Ok, sent

[Francois]

Well, in fact, it is not a bug, but one of the old weight that MMF2 has to carry since K&P.
Europress did not want the string object to be fully destroyed, so that you can continue to use them for calculations.
So the last string object of one kind, when destroyed with the destroy action, is NOT destroyed, but hidden. There is always one string of each kind in the application.
We will get rid of all these kind of things in MMF3.

[JoKa]

That makes sense, but in my example the problem is not the last remaining string, I don't even try to destroy this one. There are 3 instances of this string and I want to destroy only 2 of them. They become invisible, but if I create an AO at the string's position there appears not a single AO at the remaining string. There are 3 AOs, two of them at positions of the "destroyed" strings. It looks like all instances of the string still exist somehow. Isn't this a different issue?

[Francois]

Do you create the object in the same game loop than the one where you destroyed them? The objects are only really destroyed at the end of the loop. This could explain it.

[JoKa]

The strings already exist. To avoid any timing issues I have separated the destruction of the strings and the creation of AOs at their position. Both actions have to be triggered by user input. Should I send my demo of this problem again?