Also unclear.
Anke: In my routine âloopIMAGENESâ there is more instructions that only Sound. I don't know exactly which instruction is causing the conflict in iOS. I removed the routine after the Open Other Screen event and my problem has been solved. I'm reporting this to help others review it carefully in cases of conflict when someone puts instructions in their app behind an Open Screen block.
Again, where is the problem/difference to put this block before the open another screen block?
Try to get Screen2 to activate/open faster, for example.
Why would that change anything? It doesn't.
To switch between screens faster, you should close Screen1, as I already mentioned.
As I already mentioned I can not close the Screen1 because I need to return Screen1 on the exactly execution point when I call the Screen2. And for this raison I look for other solutions to achive better ways to open faster the Screen2
Ok, but please answer this...
So, whether you position the block before or after open another screen block.
Because if I have two threads running in parallel, I imagine it would be faster than in series.
Sorry, but I don't understand that at all.
It's just about the order of the blocksâspecifically, whether they come before or after the "open another screen" block.
I am assuming that the Open Other Screen event is an ASYNCHRONOUS process that can run simultaneously with the instructions that follow that block; this is true in Android but in iOS has a runtimes errors.
It is NOT an event. After the other screen (e.g. Screen2) is opened, the Screen2.Initialize event is triggered.
OK, but while Screen2 is opening (initilize) I can be performing operations on Screen1 simultaneously. Is this right?
In any case, I can say with certainty that if I put instructions after Open Other Screen in iOS, I I will possibly be able to runtime errors. And I might not see them with the change or transition to the Screen2.
Which operations?
For example, a timer can run on Screen1 even if it is in the background.
One reason more to put the block before the open another screen block.
But the instructions inside this timer can produce runtime errors in Screen1 if I change to a Screen2.
But I have not a faster transition to Screen2 in iOS.
But then, these runtime errors no longer occur on iOS.
And it doesn't change anything on Android.
It is wrong. In Android I have not runtime errors with instructiosns after Open Another Screen. I Have runtime errors only in iOS And you probably won't see them visually with the change or transition to Screen2
I didn't claim that, either.
I simply said that nothing changes with Android, regardless of whether you place the block before or after the "open another screen" block.
I tested it extensively using the IPA, and naturally, I see the runtime errors on iOS. However, these only occur if you place the block after the "open another screen" block.
See the turbak paper