The user isn't asking for a way to quit, just for a controlled exit.
Typically this is done from the entry screen (the Home stack in this case)
when the Back button is pressed. Right now the app says "you are home" and
blocks the backKey message. Instead, ask if they want to quit and if so,
Sannyasin Brahmanathaswami wrote:
> I have two requests that there be way to quit the app.
Few apps have that. Why do those users want this?
> I may not have got that right… or maybe there are nuances about the
> way Android works. Can you remind to Best Practice?
Mobile OSes present a very
Yay! The SivaSiva app works well on Android. 1 ½ years in the making!
I have two requests that there be way to quit the app.
But I recall you telling me that "User knows how to quit." And that "quit" was
not an important function in the app itself.
I may not have got that right… or maybe
On 23/12/2016 3:46 AM, Richard Gaskin wrote:
J. Landman Gay wrote:
> I did write about it but I hadn't tried it yet. You were right on
> the nose, that fixes it. I had to allow a short wait. This fails
> as before:
>
>tsNetClose
>quit
>
> But this works:
>
>tsNetClose
>wait 1
I just had an interesting Android quit issues. I have to check if this is an
Android problem only or a characteristic of the base engine. I wonder if
this is related to stopping the debugger in the IDE and have some calling
handler do something?
Command test1
Repeat while not test2()
Answer
Point taken. However, being an IT person and having to work with customers to
resolve their issues, I find that regularly, the user will miss some critical
piece of information that would take me right to the problem. Not only that, I
have found that more times than I would like to admit, the
To be fair, a test stack isn't always required. They're actually pretty
flexible about that. What I meant in my post was that if the test does,
in fact, need a stack in order to adequately report it, I tend to
procrastinate because I'm almost always in the middle of something else.
If there's
IMO, having a *requirement* for a user to create a test stack - EVEN IF
THE SIMPLE DESCRIPTION IS CLEAR AND UNAMBIGUOUS - is an unacceptable
bureaucratic nonsense.
I'm all in favour of creating test stacks to demonstrate a problem -
esp. if the originally failing stack is complex, or if this
On 12/22/16 11:46 AM, Richard Gaskin wrote:
I would like to think that the introduction of the new external would
not require us to rewrite our apps.
Have you filed a bug report on that?
No, for a couple of reasons. First, it doesn't seem much different than
the need to close all running
J. Landman Gay wrote:
> I did write about it but I hadn't tried it yet. You were right on
> the nose, that fixes it. I had to allow a short wait. This fails
> as before:
>
>tsNetClose
>quit
>
> But this works:
>
>tsNetClose
>wait 1 with messages
>quit
>
> Success! :)
I would
..@lists.runrev.com> on behalf of
jac...@hyperactivesw.com <mailto:jac...@hyperactivesw.com>> wrote:
I have an Android app with a simple handler:
on doQuit
quit
end doQuit
It quits as directed. On relaunch it crashes. On a second relaunch it
works fine. This is consistent behavior.
I have tr
>>>>
>>>>
>>>>
>>>> On 12/20/16, 9:38 PM, "use-livecode on behalf of J. Landman Gay"
>>>> <use-livecode-boun...@lists.runrev.com
>>>> <mailto:use-livecode-boun...@lists.runrev.com> on behalf of
>>&g
e-boun...@lists.runrev.com on behalf of
>>> jac...@hyperactivesw.com> wrote:
>>>
>>>> I have an Android app with a simple handler:
>>>>
>>>> on doQuit
>>>> quit
>>>> end doQuit
>>>>
>>>> It
nt behavior.
I have tried sending "quit" in 0, locking messages, etc. How do you
cleanly quit an Android standalone?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
__
ond relaunch it
works fine. This is consistent behavior.
I have tried sending "quit" in 0, locking messages, etc. How do you
cleanly quit an Android standalone?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
behalf of
jac...@hyperactivesw.com> wrote:
>I have an Android app with a simple handler:
>
>on doQuit
> quit
>end doQuit
>
>It quits as directed. On relaunch it crashes. On a second relaunch it
>works fine. This is consistent behavior.
>
>I have tried sending "quit&quo
I have an Android app with a simple handler:
on doQuit
quit
end doQuit
It quits as directed. On relaunch it crashes. On a second relaunch it
works fine. This is consistent behavior.
I have tried sending "quit" in 0, locking messages, etc. How do you
cleanly quit an Android
17 matches
Mail list logo
