Sweet!
Bob S
> On Dec 9, 2014, at 09:46 , J. Landman Gay wrote:
>
> That only happens in the IDE, you can lock messages before quitting. Or,
> what I usually do from the message box: delete this stack. (Or you can use
> the menu option to remove from memory.) Then a regular quit doesn't ask
Are you saying locking messages before quitting prevents the Save dialog from
presenting? I didn’t know that.
Bob S
> On Dec 8, 2014, at 09:29 , Ray wrote:
>
> I just issue the command "quit". You might consider saving first or, if you
> don't want any interruptions, locking messages first
Jim,
Great idea! There are s many ways to do things in LC.
Bill
On Dec 8, 2014, at 1:58 PM, Jim Lambert wrote:
> I suggested doMenu because Bill said selecting Quit from the menu worked
> while a button with ‘quit’ didn’t.
>
> But he reports that doesn’t work for him either, so perhaps doM
I also use "close this stack" from the message box.
Regards,
Scott Rossi
Creative Director
Tactile Media UX/UI Design
> On Dec 9, 2014, at 9:46 AM, J. Landman Gay wrote:
>
> That only happens in the IDE, you can lock messages before quitting. Or,
> what I usually do from the message box: del
That only happens in the IDE, you can lock messages before quitting. Or, what
I usually do from the message box: delete this stack. (Or you can use the menu
option to remove from memory.) Then a regular quit doesn't ask.
On December 9, 2014 11:25:36 AM CST, Bob Sneidar
wrote:
>My perennial q
Richard:
Got your logger stack. I’m in a huge crunch right now, so I need to just go
ahead and delete my quit button, and use the toolbar menu to quit, for a bit.
I’m getting ready for a geophysics meeting in San Francisco, then Hawaii until
Jan. 1. I’ll try to get to it but got a bunch of thing
Any open drivers also prevent quitting, or it used to.
On December 9, 2014 8:59:32 AM CST, Richard Gaskin
wrote:
>William Prothero wrote:
>
> > On Dec 8, 2014, at 2:10 PM, Richard Gaskin wrote:
>
>For an app to successfully quit two conditions must be met:
>1. All stacks are closed
>2. All pend
My perennial question is, how do I quit without saving the stack or even
asking? There ought to be a “close without saving” variation.
Bob S
On Dec 7, 2014, at 15:25 , Colin Holgate
mailto:co...@verizon.net>> wrote:
Try this instead:
on mouseup
quit
end mouseup
__
William Prothero wrote:
There really is no code in the quit button. I just do:
——Method 1 --
on mouseUp
quit
end mouseUp
Or:
——Method 2 --
on mouseUp
send “doTheQuit” to me in 0 seconds
end mouseUp
on doTheQuit
quit
end doTheQuit
I tried closing all substacks. Do I need to cl
Richard:
There really is no code in the quit button. I just do:
——Method 1 --
on mouseUp
quit
end mouseUp
Or:
——Method 2 --
on mouseUp
send “doTheQuit” to me in 0 seconds
end mouseUp
on doTheQuit
quit
end doTheQuit
I tried closing all substacks. Do I need to close the mainstack
William Prothero wrote:
> On Dec 8, 2014, at 2:10 PM, Richard Gaskin wrote:
>> Interesting. Any pending messages at the time quit is invoked?
>
> I tried doing “Lock messages” before the quit, and closing
> unused stacks, but it didn’t seem to make any difference.
> Apparently the toolbar menu q
Richard:
I tried doing “Lock messages” before the quit, and closing unused stacks, but
it didn’t seem to make any difference. Apparently the toolbar menu quit command
does some kind of cleanup before it actually quits.
Re the system log, I don’t usually try to interpret that. There is a large
c
William Prothero wrote:
> I’ve tried a number of things to get my app to shut down without
> crashing the app. I know it must be possible because the toolbar
> menu quits fine. I may just stop trying to use a script to quit.
> It’s not essential since the toolbar menu quits fine. Anyway, I’ve
> t
I suggested doMenu because Bill said selecting Quit from the menu worked while
a button with ‘quit’ didn’t.
But he reports that doesn’t work for him either, so perhaps doMenu doesn’t
really 'do menu' under the hood.
If the Quit accelerator key combination also works (command-Q on Mac) then I’d
Richard:
Thanks for the input. I’ll stop messing with the doMenu approach. I’ve tried a
number of things to get my app to shut down without crashing the app. I know it
must be possible because the toolbar menu quits fine. I may just stop trying to
use a script to quit. It’s not essential since t
William Prothero wrote:
I got no response from the doMenu command, so perhaps I needed
to include the shortcut key in the name?
DoMenu is pretty limited in LiveCode. It was necessary in HyperCard
because that language wasn't rich enough to build an entire IDE in, so
the only way you could i
Ray and Jim:
Tnx for the suggestions. Tried both. I did lock messages prior to the quit
statement. I couldn’t get the toolbar menu to fire on quit. The menu is
“PT_Explorer” and the item I want is “Quit PT_Explorer”. So I did
domenu “Quit PT_Explorer” of menu “PT_Explorer”
I got no response fro
I just issue the command "quit". You might consider saving first or, if
you don't want any interruptions, locking messages first.
On 12/8/2014 2:04 PM, Jim Lambert wrote:
Prothero wrote:
why won?t the button work when the toolbar menu does. Obviously, there?s a
difference in the way each wor
> Prothero wrote:
>
> why won?t the button work when the toolbar menu does. Obviously, there?s a
> difference in the way each works.
What happens if you
doMenu “Quit” from menu [appName]
?
Jim Lambert
___
use-livecode mailing list
use-livecode@lis
Colin:
I tried closing the browser window (on the card where I had the quit button)
and it still crashes.
BUT, I did a test stack, made a standalone, and the quit button works. Hm.
Wonder what it could be. My application stack is pretty big and complex, but
….. I don’t think any handlers are
A bare bones test seems not to crash. Look for any handlers you have that are
still doing something at the time you quit.
BTW, I was testing the idea with v7.01 rc3.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
Colin:
I did try that and it crashed the app too. That’s why I tried to delay the quit
until it got through doing the mouseDown handler.
Bill
On Dec 7, 2014, at 3:25 PM, Colin Holgate wrote:
> Try this instead:
>
> on mouseup
>quit
> end mouseup
>
>
Try this instead:
on mouseup
quit
end mouseup
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecod
Folks:
I don’t know if this is needed anyway, but I have a button on one of my screens
whose intention is to quit the application. The code is;
on mouseUp
send “quit” to me in 0 seconds
end mouseUp
This crashes the application. The menu that the standalone creates, in the menu
bar also
24 matches
Mail list logo
