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
item, you can dispatch a menuPick
handler to the relevant menu button in revMenubar with the name of the
menu item as its param.
But quit is very essential - every app needs it - so that's built right
into the language with the quit command.
If you need to do any processing before the app
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
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
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
tried
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
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
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
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 co...@verizon.net wrote:
Try this instead:
on mouseup
quit
end mouseup
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
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
On 7/23/13 3:34 PM, Łukasz Józwiak wrote: SET PUT is not same look in
rev docs, and SET work for me always PUT only
at start. look:
in app file
I'm familiar with the behavior of put and set, it's been many years.
;) You can't attach files to this mailing list, so we can't see what you
to true
put the RTFtext of fld DoneText of card Entry of stack
RWord into url(file: BacktUp .rtf)
set the lockScreen to false
set the vis of img SAVE to false
end if
---
Quit
---
end mouseUp
Richmond.
___
use-livecode
set the lockScreen to true
put the RTFtext of fld DoneText of card Entry of stack
RWord into url(file: BacktUp .rtf)
set the lockScreen to false
set the vis of img SAVE to false
end if
---
Quit
---
end mouseUp
What do you see when you run
then
set the vis of img SAVE to true
set the lockScreen to true
put the RTFtext of fld DoneText of card Entry of stack RWord
into url(file: BacktUp .rtf)
set the lockScreen to false
set the vis of img SAVE to false
end if
---
Quit
---
end mouseUp
Richmond
is not empty
then
set the vis of img SAVE to true
set the lockScreen to true
put the RTFtext of fld DoneText of card Entry of stack
RWord into url(file: BacktUp .rtf)
set the lockScreen to false
set the vis of img SAVE to false
end if
---
Quit
Richmond wrote:
On 03/30/2013 05:22 PM, Richard Gaskin wrote:
...
What do you see when you run it after adding this line immediately
below the one that writes the file?:
answer RESULT: the result SYSERR: sysError()
RESULT: SYSERR: 2
Which OS?
On Windows I believe 2 refers to an
perform similarly; save a
document in the folder of the standalone but deliver the ERROR message.
HOWEVER, in all cases I have commented out the QUIT command, and wonder
if that is happening so quickly the standalone has no time to export the
back-up file
Err . . . thinking on my feet here
Thomas McGrath III mcgrath3@... writes:
Will: kill 9 process MyApp.app which should work on the Mac also work on
windows if I change it to: kill 9 process MyApp.exe
Found this:
http://www.tech-recipes.com/rx/446/xp_kill_windows_process_command_line_taskkill/
--
Mark Wieder
Thanks Mark,
I am reading it now.
Tom
-- Tom McGrath III
http://lazyriver.on-rev.com
mcgra...@mac.com
On Mar 4, 2013, at 5:15 PM, Mark Wieder mwie...@ahsoftware.net wrote:
Thomas McGrath III mcgrath3@... writes:
Will: kill 9 process MyApp.app which should work on the Mac also work on
I am trying to quit another application that I launched from LC when my
standalone quits. Kill seems acceptable since the other app has no clean up
etc. -- I'm even thinking with extreme prejudice might be appropriate for this
app. I have both a Mac and Windows versions of the other app
...@gmail.comwrote:
So, a besetting problem of my Devawriter is that as it closes down on Quit
the end-user is subjected to an entertaining light-show where the main
stack and the
substacks appear and disappear several times.
This is NOT GOOD.
I would be grateful if anyone could put me
do the trick.
Bernard
On Sun, Dec 16, 2012 at 12:37 PM, Richmond richmondmathew...@gmail.comwrote:
So, a besetting problem of my Devawriter is that as it closes down on Quit
the end-user is subjected to an entertaining light-show where the main
stack and the
substacks appear and disappear
So, a besetting problem of my Devawriter is that as it closes down on Quit
the end-user is subjected to an entertaining light-show where the main
stack and the
substacks appear and disappear several times.
This is NOT GOOD.
I would be grateful if anyone could put me straight in this respect
On 2/23/12 10:55 PM, ilsa wrote:
Hi:
Thanks. I was trying the below in my stack script, which I got from a
Jacquie message on the list:
global gFP
on appleEvent pClass, pID
if pClass is aevt and pID is odoc then
-- the file path is in the appleEvent data
request appleEvent
Folks,
I think that AppleEvents are not authorized on the new Mac App Store rules
right?
Silly Apple...
Andre
On Fri, Feb 24, 2012 at 4:24 PM, J. Landman Gay jac...@hyperactivesw.comwrote:
On 2/23/12 10:55 PM, ilsa wrote:
Hi:
Thanks. I was trying the below in my stack script, which I got
On 2/24/12 1:44 PM, Andre Garzia wrote:
Folks,
I think that AppleEvents are not authorized on the new Mac App Store rules
right?
I hadn't even thought of that. I bet you're right. I wonder if Automator
will still ship with Mt Lion.
--
Jacqueline Landman Gay |
Andre Garzia wrote:
I think that AppleEvents are not authorized on the new Mac App Store rules
right?
I hope that any limitation with Apple events is limited to sending them;
for many years apps have been required to receive and respond to the
odoc event as the means of opening apps.
--
Well then screw the app store! I am starting to look sideways at Apple...
Bob
On Feb 24, 2012, at 11:44 AM, Andre Garzia wrote:
Folks,
I think that AppleEvents are not authorized on the new Mac App Store rules
right?
Silly Apple...
Andre
On Fri, Feb 24, 2012 at 7:26 PM, Bob Sneidar b...@twft.com wrote:
Well then screw the app store! I am starting to look sideways at Apple...
There will be a day in the not so distant future when if you don't sell
your software on mac apple store, the mac users will never discover it
(unless
I'll have to say negative to both of your assertions. There are a very broad
number of applications that do not fit the model of the MAS and Apple knows
this. As long as there are software stores, integration consultants, and
non-home user customers, there will always be a normal channel for
Thanks, but it still doesn't work. Do I have to enable dropability
somewhere, or enter some special standalone settings?
Thanks,
ilsa
On Fri, Feb 24, 2012 at 10:24 AM, J. Landman Gay
jac...@hyperactivesw.com wrote:
On 2/23/12 10:55 PM, ilsa wrote:
Hi:
Thanks. I was trying the below in my
Tim,
Just checked the documentation at:
https://developer.apple.com/library/mac/documentation/Miscellaneous/Reference/EntitlementKeyReference/AppSandboxTemporaryExceptionEntitlements/AppSandboxTemporaryExceptionEntitlements.html#//apple_ref/doc/uid/TP40011195-CH5-SW3
Yes you will be able to
On 2/24/12 4:08 PM, ilsa wrote:
Thanks, but it still doesn't work. Do I have to enable dropability
somewhere, or enter some special standalone settings?
You shouldn't have to do anything special. Did you put in some answer
dialogs to see if the handler actually runs at all? It sounds like
The app icon in the Dock doesn't hilite when I drag a jpg over it.
When the app opens I get the oapp pID.
ilsa
On Fri, Feb 24, 2012 at 2:43 PM, J. Landman Gay
jac...@hyperactivesw.com wrote:
On 2/24/12 4:08 PM, ilsa wrote:
Thanks, but it still doesn't work. Do I have to enable dropability
On 2/24/12 6:15 PM, ilsa wrote:
The app icon in the Dock doesn't hilite when I drag a jpg over it.
When the app opens I get the oapp pID.
I see, that's a whole different problem. You need to tell the OS that
your app will accept jpgs, or any other file type you want to work with.
You can do
It worked when I put those extensions in the standalone prefs! And
when I drag several files the full paths of all get put into the test
field as paragraphs. Perfect. I put JPEG into the Doc Types field
too but when I dragged a .png onto it, it also showed up, so
fantastic! I appreciate all the
To follow up, by putting into the Document Type standalone
pref, folders are handled. However, then all files with any extension
are also handled. The appleevent pID is odoc for both files and
folders. I should be able to filter the apple event data to pick out
what I want to operate on.
On 2/24/12 10:42 PM, ilsa wrote:
To follow up, by putting into the Document Type standalone
pref, folders are handled. However, then all files with any extension
are also handled. The appleevent pID is odoc for both files and
folders. I should be able to filter the apple event data to pick
Hi:
I've searched the list but haven't found out how to do a very simple
thing: drop an image file, or a bunch of image files, onto a
standalone and have it process them all and then quit. So I could have
the app in the Dock and drop files on it. I have the image processing
part down, but getting
ilsa wrote:
I've searched the list but haven't found out how to do a very simple
thing: drop an image file, or a bunch of image files, onto a
standalone and have it process them all and then quit. So I could have
the app in the Dock and drop files on it. I have the image processing
part down
:
I've searched the list but haven't found out how to do a very simple
thing: drop an image file, or a bunch of image files, onto a
standalone and have it process them all and then quit. So I could have
the app in the Dock and drop files on it. I have the image processing
part down, but getting
AFAICS, iOS apps don't have an overt 'quit' button, since simply pressing the
physical button on the device (I forgot its name) quits whatever is running.
However this isn't quite right is it, since apps can go on being present and
maybe actually running in the background
LC iOS apps don't stay alive when you quit them with the Home button. You can
save and restore things to give the impressions of a quit and resume, but the
app itself is killed when you quit.
In my experience the on shutdown command is the best place to put stuff you
want to do when the app
not killed. I'm sure there are lots of other examples...
what is going on in these cases?
Graham
Sent from my iPad
On Sun, 19 Feb 2012 21:44:09 +1100, Gerry Orkin gerry.or...@gmail.com
LC iOS apps don't stay alive when you quit them with the Home button. You can
save and restore things to give
On Feb 19, 2012, at 1:43 PM, Graham Samuel wrote:
Gerry, thanks for replying.
That's what happens to my simple little app, but what about my favourite
radio app, TuneIn Radio? It's feeding the BBC to me as I write this, but I
could only access Mail by pressing the Home button after
Yup, LC apps can't take advantage of background functioning...yet. Hopefully
that will change in a future release.
Gerry
On 20/02/2012, at 12:12 PM, Ken Ray wrote:
I assume is the case with LC apps.
___
use-livecode mailing list
Good idea, thanks Jacque.
On Fri, Jan 20, 2012 at 10:06 PM, J. Landman Gay
jac...@hyperactivesw.comwrote:
On 1/20/12 11:57 PM, Pete wrote:
The problem is, I want toc lose the stack but leave the application
running. If I pass closeStackRequest, I believe the app will quit
(Standalone
Hi Pete,
This is correct behaviour. You'r be very surprised if you close the last window
on Windows and your app continues running but is completely inaccessible. You'd
also be surprised of your standalone behaved differently on Mac. Moreoever,
without a window, you need a menubar with a Quit
If you take the splash stack approach and hide the splash stack before
launching the actual app stack, it won't do that. But you would have to have
some way of launching the app stack again, like a system menu in the splash
stack.
Bob
On Jan 19, 2012, at 10:25 PM, Pete wrote:
It seems
the windows for an application and the application's menu bar is
still there at the top of the screen, including a Quit item on the
Application menu.
As far as I can tell, all Mac applications work this way. Closing the last
open window in the app and quitting it are two different activities. Even
, and I think Apple has
issued its official opinion on this which does allow for this behavior.
One could use the closestack message to open a dialog with a menubar,
which ask the user if they would like to open another window or quit the
app, or some other option appropriate for the app.
Warren
System Preferences is an example of an app that quits when you close the window.
On Jan 20, 2012, at 12:53 PM, Warren Samples wrote:
On 01/20/2012 11:23 AM, Pete wrote:
As far as I can tell, all Mac applications work this way..
This is not correct. It depends on what kind of application
and is a utility (I
think, can't exact recall), the app should quit when the window is
closed. System Preferences works that way. But for most of us, that
doesn't apply.
The fix is to open an invisible anchor stack, either with its vis set
to false, or just placed offscreen. You don't need to do that on any
window and is a utility (I
think, can't exact recall), the app should quit when the window is closed.
System Preferences works that way. But for most of us, that doesn't apply.
The fix is to open an invisible anchor stack, either with its vis set to
false, or just placed offscreen. You don't need
On 1/20/12 2:00 PM, Pete wrote:
Thanks Jaccue. So I can't use a closeStack or shutdown message handler to
control this?
Pete
Old habits die hard so I've always used the dummy stack method. But now
that you mention it, yes, I think you could trap the closeStackRequest
message. That would be
OK, thanks Mark and Jacque. It sounds like the shutdownRequest message
will do the job - if I don't pass it, the application should stay open.
I'll have to figure out how to deal with the user selecting Quit from the
Application menu, or the user shutting down their computer since I really
do
with the user selecting Quit from the
Application menu, or the user shutting down their computer since I really
do need to quit then.
I think it would be better to use closeStackRequest. That message is only
sent when the user manually clicks in the close box, so you don't need to
worry about
On 1/20/12 11:57 PM, Pete wrote:
The problem is, I want toc lose the stack but leave the application
running. If I pass closeStackRequest, I believe the app will quit
(Standalone) and if I don't pass it, the window will stay open, neither of
which is what I need to happen. But maybe I can
It seems that when you close the main stack window in an LC standalone
application on OS X, the application terminates. That doesn't seem like
normal behavior for an OS X application, at least not the ones I'm familiar
with. Maybe there's no right or wrong on this and it's a function of the
In the Menu Builder, I have always set Quit for the Mac with the Mnemonic
checked and set to Q alone with the Shortcut set to Command. I frequently use
a Quit button in my apps which the user could quit an app.
I just noticed a few days ago that this keyboard combination of Command + Q
works
On Sat, Oct 1, 2011 at 1:07 PM, Charles Szasz wrote:
In the Menu Builder, I have always set Quit for the Mac with the Mnemonic
checked and set to Q alone with the Shortcut set to Command. I frequently
use a Quit button in my apps which the user could quit an app.
I just noticed a few days
On Oct 1, 2011, at 12:07 PM, Charles Szasz wrote:
In the Menu Builder, I have always set Quit for the Mac with the Mnemonic
checked and set to Q alone with the Shortcut set to Command. I frequently
use a Quit button in my apps which the user could quit an app.
I just noticed a few days
Oh right! That was it.
Bob
On Sep 13, 2011, at 3:44 PM, Dar Scott wrote:
I have seen a hang in the IDE when there is an answer/ask during quitting.
On OS X you can use the Console for looking at both error messages (even your
own written to stdout) and crash logs.
Dar
I'm trying to track an occasional freeze crash of LiveCode. It happens when
I shut-down the stack after closing the Valentina database connection. I
have code that checks to see if the database is already shut down and my
error message comes up saying: database already closed and then it
freezes.
Are you using alternative debuggers? I have discovered that the one I use will
sometimes lock if I generate an error on quit. It may be something I am doing
wrong so I will not name it here, but it was pretty pervasive. Make sure you
don't have breakpoints in your closestack handler. It may
alternative debuggers? I have discovered that the one I use
will sometimes lock if I generate an error on quit. It may be something I am
doing wrong so I will not name it here, but it was pretty pervasive. Make
sure you don't have breakpoints in your closestack handler. It may be
nothing but I have had
I have seen a hang in the IDE when there is an answer/ask during quitting.
On OS X you can use the Console for looking at both error messages (even your
own written to stdout) and crash logs.
Dar
On Sep 13, 2011, at 3:25 PM, william humphrey wrote:
I'm trying to track an occasional freeze
That's something I hadn't considered. I'll change it so the dialogue
doesn't come up on quit (only when that stack is closed).
Thanks.
On Tue, Sep 13, 2011 at 6:44 PM, Dar Scott d...@swcp.com wrote:
I have seen a hang in the IDE when there is an answer/ask during quitting
the dialogue
doesn't come up on quit (only when that stack is closed).
Thanks.
On Tue, Sep 13, 2011 at 6:44 PM, Dar Scott d...@swcp.com wrote:
I have seen a hang in the IDE when there is an answer/ask during quitting.
--
http://www.bluewatermaritime.com
...@bluewatermaritime.com wrote:
That's something I hadn't considered. I'll change it so the dialogue
doesn't come up on quit (only when that stack is closed).
Thanks.
On Tue, Sep 13, 2011 at 6:44 PM, Dar Scott d...@swcp.com wrote:
I have seen a hang in the IDE when there is an answer/ask during
crashes on quit
I've just started having a problem. LivCode crashes my 10.6.8 OS when I
quit
it. I even tried updating to LiveCode 4.6.2 and it still crashes when I
quit.
I can start LiveCode and do nothing or open and close stacks, doesn't
matter, but when I quit LiveCode everything goes down
I've just started having a problem. LivCode crashes my 10.6.8 OS when I quit
it. I even tried updating to LiveCode 4.6.2 and it still crashes when I
quit.
I can start LiveCode and do nothing or open and close stacks, doesn't
matter, but when I quit LiveCode everything goes down.
Can anyone help
Deleting the My LiveCode folder solves the problem.
On Tue, Jun 28, 2011 at 7:16 PM, william humphrey
b...@bluewatermaritime.com wrote:
I've just started having a problem. LivCode crashes my 10.6.8 OS when I
quit it. I even tried updating to LiveCode 4.6.2 and it still crashes when I
quit
: Tue, Jun 28, 2011 7:16 pm
Subject: LiveCode crashes on quit
I've just started having a problem. LivCode crashes my 10.6.8 OS when I quit
it. I even tried updating to LiveCode 4.6.2 and it still crashes when I
quit.
I can start LiveCode and do nothing or open and close stacks, doesn't
matter
' since temp is not
persistent between launches.
Kind regards
Bernd
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/iOS-quit-app-message-tp3403873p3404781.html
Sent from the Revolution - User mailing list archive at Nabble.com
Hi all
Is there any way to detect the closing of an iOS app? As far as I can tell
closestack and suspendstack don't work.
Cheers
Gerry
-- photo site: http://gerryorkin.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
On 3/24/11 4:29 PM, Gerry wrote:
Hi all
Is there any way to detect the closing of an iOS app? As far as I can
tell closestack and suspendstack don't work.
Does the shutdown message get sent? I haven't tried it but it sounds
logical.
--
Jacqueline Landman Gay |
, claiming it was
saving them all. Then I quit the application. LC opened up every stack with a
script in it that had been changed (and presumably saved) and asked me if I
wanted to save it!!
In the past, I've complained about being able to quit LC and not always getting
a warning about
On Jan 9, 2011, at 7:40 AM, Richmond wrote:
I want to disable the ability of Mac users to QUIT
by pressing Command-Q; tis is to force them to
use localised QUIT buttons (each with slightly
different characteristics) on cards within a stack.
This is in my saved tidbits stack, from a discussion
I want to disable the ability of Mac users to QUIT
by pressing Command-Q; tis is to force them to
use localised QUIT buttons (each with slightly
different characteristics) on cards within a stack.
___
use-livecode mailing list
use-livecode
101 - 181 of 181 matches
Mail list logo
