Jacque:
> I did a test before answering and the message was sent to the card
> of my otherwise blank stack, after dismissing the IDE dialog.
Same here!
Bob:
> there have been at least 2 versions that were unstable that crash
> to desktops were not uncommon, and after losing so much data, I
>
Nice try but sadly it does not work. The message does not even get sent to the
stack script.
Bob S
On Feb 4, 2021, at 5:22 PM, Mark Wieder via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On 2/4/21 4:19 PM, Bob Sneidar via use-livecode wrote:
NVM I found this bug has already bee
Not sure. If the stack is “dirty” I get the save dialog BEFORE
closeStackRequest, which is what I am trying to avoid.
To others, I know this is not a good idea in general, but since there have been
at least 2 versions that were unstable that crash to desktops were not
uncommon, and after losing
Thanks all for your suggestions. I will try various methods.
As to the propriety of certain methods, I suppose in answer to why do it that
way, to quote another thread, “Because we can!” :-)
Bob S
___
use-livecode mailing list
use-livecode@lists.runr
On 2/4/21 6:33 PM, Curry Kenworthy via use-livecode wrote:
The preOpenStack handler is NOT ideal for this type of cleanup.
"Literally, to "clear the fields" of a stack."
(And now we also know, a "complex" stack.)
That is NOT something best done in preOpenStack.
A complex stack usually has multi
Mark:
> I agree with others that this isn't a Good Idea,
> and a cleaning routine in preOpenStack would do the trick nicely.
Amen, Brother Mark! Good Idea to avoid Bad Habits.
(Agreed, except a small but crucial difference in details)
As Tore said:
> execute the necessary routines as part
I did a test before answering and the message was sent to the card of my
otherwise blank stack, after dismissing the IDE dialog. That makes me think
something is going on with your particular stack. What happens if you try
it with a plain new stack?
--
Jacqueline Landman Gay | jac...@hyperacti
e-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay via use-livecode
Sent: Thursday, February 04, 2021 5:53 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Close Stack Cleanup
There used to be a gREV* global variable that tracked the dirty status and
if the stack was dirt
On 2/4/21 4:19 PM, Bob Sneidar via use-livecode wrote:
NVM I found this bug has already been submitted… IN 2008! LOL!
https://quality.livecode.com/show_bug.cgi?id=4617 Hey Kevin!
Looking at that, here's a (completely untested) suggestion:
The revIDEHandleCloseStackRequest handler is in the I
NVM I found this bug has already been submitted… IN 2008! LOL!
https://quality.livecode.com/show_bug.cgi?id=4617 Hey Kevin!
Bob S
On Feb 4, 2021, at 4:05 PM, Bob Sneidar via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Thanks Ralph. Actually what I am looking for is a message t
Thanks Ralph. Actually what I am looking for is a message that gets sent when
the close button of a window gets clicked. The Message Watcher seems to
indicate not (or rather fails to indicate). I think this is a bug, or at least
an oversight. This means that anyone can close a stack, and closeSt
ecode-boun...@lists.runrev.com] On Behalf Of
J. Landman Gay via use-livecode
Sent: Thursday, February 04, 2021 5:53 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Close Stack Cleanup
There used to be a gREV* global variable that tracked the dirty status and if
the stack was dirty it p
Back to the drawing board. This does NOT work when clicking the red dot.
Bob S
On Feb 4, 2021, at 3:10 PM, Bob Sneidar via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Thanks for the reply Jacque. I ran the message watcher while clicking the red
dot. None of the messages that a
Thanks Curry. That works for the IDE, but not for the standalone. End Users do
not save their stacks, as I give them no way to do so. The stacks in my app
perform two functions: An interface to control the app and also a place to
store persistent data i.e. properties. If a user force-quits my ap
Tore:
> I do not do any clean up at closing time. Instead I execute
> the necessary routines as part of a preOpenStack handler.
> I then do not have to consider which way the stack was closed.
Yes! Like you, for cleanup I also avoid that how-closed consideration.
Much easier to have a simpler
It’s my understanding that I am unable to reference objects on a card of a
stack in a preOpenStack handler. Referencing an object in the stack opens the
stack triggering a race condition which continually triggers preOpenStack. That
is from memory though.
Bob S
On Feb 4, 2021, at 2:50 PM, Tor
Thanks for the reply Jacque. I ran the message watcher while clicking the red
dot. None of the messages that appear have anything to do with closing the
stack.
Here’s what I came up with. The closeStackRequest is NOT getting sent to the
current card as the dictionary indicates, although the tar
There used to be a gREV* global variable that tracked the dirty status and if the stack was
dirty it put up the "do you want to save?" dialog. I can't find it now so something has
changed. When it existed, you could toggle that variable via script and the IDE wouldn't bother
you.
The IDE does
Performing the clean up in preOpenStack makes it happen before the stack is
visible, at least according to the dictionary.
"Unlike openStack <>, preOpenStack handlers <> are executed <> before the stack
window <> appears. Because of this, the preOpenStack handler <> is a good place
to put code
Thanks for the response Curry and Tore.
The reason I clean up at close is because when I open the stack the next time I
do not want to remains of what I was doing before to show. It’s a small point
but it look cleaner if the first time opening the stack there is nothing in the
fields. All atte
I follow a similar approach to what Curry describes here, keeping it modular,
but I do not do any clean up at closing time. Instead I execute the necessary
routines as part of a preOpenStack handler. I then do not have to consider
which way the stack was closed. This is also what I encourage my
Bob:
> I am trying to clean up my stack (i.e. clear the fields),
> then save it when I close it
This is a good topic for LiveCode learners; I'm chiming in
I often do something similar - but with an important difference:
I perform cleanup when I save. I do NOT force an auto save.
(More on t
22 matches
Mail list logo
