.
I know there are a lot of posts for that.
I want to use on screen1 the otherscreenclosed event, but it always triggers the initialize event. see also here:
I open Screen2 with this method, with this block i want to be sure to close Screen1 and not to run in memory issues.
The close screen with value block.. doesnt work as it only closes screen1.
I will have a look at the manager screen you prefered.
You can use that event only together with the manager screen method
You are using a variation of the Tribblehunter method... which means, there is only 1 screen open at any time and the OtherScreenClosed method never will get triggered
The manager screen method is working fine now, great Taifun .
The only thing i am missing is the start value which i need to forward from
Screen2 to Screen1. I used it with the Tribblehunter method without TinyDB.
Can i do this also with the manager screen method?
You are right, the if then logic is the only way i can manage it.
When Screen1 initialize first time i have to use an if then block like below, i need to use a TinyDB "Neustart" tag to check if the Screen1 is opened by Initialize or if it returns from Screen2 because the OtherScreenClosed event doesnt work with a start value for me.
The problem is that Screen1 always starts only by initialize event and when the user is closing the app or uses backpressed block the TinyDB start tag has always to be resetted to true. But with OtherscreenClosed and the manager screen tip from @Taifun i have no opportunity to use the start value from Screen2.
My workaround with the ActivityStateChanged block is also not working, as the block is necessary in Screen2 instead of Screen1.