The following seems to process both Wait()s before the popup shows, and then dissappears too soon:
app.Wait( 1 );
app.ShowPopup("Some Text"); // should be default Long show
app.Wait( 1 );
minor Blah blahs ...
app.Exit();
Is this some quirk of the Android system's message queue prioritising, or the DroidScript bridge or something?
Is there a known work around please?
Paul
Its a small GUI-less app called from certain other apps' Share feature (browsers and text displaying apps), I wanted a small quick message showing why somethings didn't / couldn't happen as the User may have expected.
Exit() has to be called after it so it doesn't remain open, and that prematurely kills the popup as well.
A popup followed by a single Wait() also doesnt show until the postpositioned Wait() has executed as is to be expected by what you just shared I suppise.
My double Wait() was an experiment to test whether Wait()s somehow took precedence over popups.
The message then still showed after both Wait()s were finished.
So I was looking for an unobtrusive message style - may need to try and use a timer or an alert() after all :-)
Thanks,
paul
though the setTimeout often calls a function that cleans up before it exits.
Paul