W walt61 Well-Known Member Licensed User Longtime User Feb 14, 2015 #1 Having used Visual Studio for many years, I've been caught out a couple times by my app behaving strangely (at least it seemed to) because I added code to a sub after calling StartActivity; code that won't get executed at all or only partially as the activity gets paused and the new one gets started. Recently it happened again and I'm sure it won't be the last time It would be useful if the compiler would issue a warning if code is found after a call to StartActivity, just as a memory jogger.
Having used Visual Studio for many years, I've been caught out a couple times by my app behaving strangely (at least it seemed to) because I added code to a sub after calling StartActivity; code that won't get executed at all or only partially as the activity gets paused and the new one gets started. Recently it happened again and I'm sure it won't be the last time It would be useful if the compiler would issue a warning if code is found after a call to StartActivity, just as a memory jogger.
Erel B4X founder Staff member Licensed User Longtime User Feb 15, 2015 #2 You are allowed to put code after StartActivity. The only exception is with modal dialogs that will return immediately with the cancel value.
You are allowed to put code after StartActivity. The only exception is with modal dialogs that will return immediately with the cancel value.
W walt61 Well-Known Member Licensed User Longtime User Feb 15, 2015 #3 Erel said: You are allowed to put code after StartActivity. The only exception is with modal dialogs that will return immediately with the cancel value. Click to expand... Thanks Erel, that's probably what happened then and I failed to see the wood for the trees.
Erel said: You are allowed to put code after StartActivity. The only exception is with modal dialogs that will return immediately with the cancel value. Click to expand... Thanks Erel, that's probably what happened then and I failed to see the wood for the trees.