Re: startUp message not being sent

Hi Tom, Am 25.02.2013 um 17:03 schrieb Thomas McGrath III : > Haa! Bang my head and call me duh! DUH! :-D > Thanks > -- Tom McGrath III > http://lazyriver.on-rev.com > mcgra...@mac.com Best Klaus -- Klaus Major http://www.major-k.de kl...@major.on-rev.com __

Re: startUp message not being sent

Haa! Bang my head and call me duh! Thanks -- Tom McGrath III http://lazyriver.on-rev.com mcgra...@mac.com On Feb 25, 2013, at 11:01 AM, Klaus on-rev wrote: > Hi Tom, > > Am 25.02.2013 um 16:46 schrieb Thomas McGrath III : > >> I was trying to set an 'on first launch' flag in the startUp messa

Re: startUp message not being sent

Hi Tom, Am 25.02.2013 um 16:46 schrieb Thomas McGrath III : > I was trying to set an 'on first launch' flag in the startUp message but it > does not seem to fire at all? Is anyone else seeing this? > > on startUp > global gFirstLaunch > put true into gFirstLaunch > end startUp "startup" can o

Re: Startup message

Startup will do what you want. To test while in the IDE, do send "startup" to stack "mymainstack" from the message box. HTH Graham On :Tue, 2 Aug 2011 13:57:14 -0700, Pete > > Thanks Richard. If I understand the message path correctly, the > preOpenStack handler in the mainstack will be ex

Re: Startup message

Behalf Of Richard Gaskin >> Sent: Tuesday, August 02, 2011 4:30 PM >> To: use-livecode@lists.runrev.com >> Subject: Re: Startup message >> >> Pete wrote: >>> Thanks folks, didn't realise this message only applied to >> standalones. Is >>> th

Re: Startup message

Thanks, makes sense. Pete Molly's Revenge On Tue, Aug 2, 2011 at 2:04 PM, Mark Schonewille < m.schonewi...@economy-x-talk.com> wrote: > Hi Pete, > > Move your script from the stack script to the card script. If you keep a > preOpenStack script in the card script,

Re: Startup message

Slava Paperno wrote: On a related note: I have often wished that preOpenStack and openStack were not called when I open the stack in the IDE. When the programming is not finished, some calls that are already written into those handlers cannot yet be successful because other parts are missing. The

Re: Startup message

Hi Pete, Move your script from the stack script to the card script. If you keep a preOpenStack script in the card script, then it won't be executed when other substacks are opened. If you want the script to execute in the standalone only and not in the IDE, then you have to options. Either put

Re: Startup message

On 8/2/11 3:49 PM, Slava Paperno wrote: On a related note: I have often wished that preOpenStack and openStack were not called when I open the stack in the IDE. When the programming is not finished, some calls that are already written into those handlers cannot yet be successful because other par

Re: Startup message

Thanks Richard. If I understand the message path correctly, the preOpenStack handler in the mainstack will be executed for every substack of the main stack that is opened? I can easily check whether my initialisation code has already executed in the handler but was hoping for a way to have the co

RE: Startup message

stigate if it's true. Slava > -Original Message- > From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode- > boun...@lists.runrev.com] On Behalf Of Richard Gaskin > Sent: Tuesday, August 02, 2011 4:30 PM > To: use-livecode@lists.runrev.com > Subject: Re

Re: Startup message

Pete wrote: Thanks folks, didn't realise this message only applied to standalones. Is there then no equivalent for stacks running in the IDE, other than a preOpenCard/preOpenStack handler? Startup is for when the engine starts up, preOpenStack is for when a stack is opened. Having both messa

Re: Startup message

Thanks folks, didn't realise this message only applied to standalones. Is there then no equivalent for stacks running in the IDE, other than a preOpenCard/preOpenStack handler? Pete Molly's Revenge 2011/8/2 Björnke von Gierke > is your stack actually the mainst

Re: Startup message

is your stack actually the mainstack of the standalone that you are starting? otherwise, it will not get any startup messages. Use preopencard or preopenstack instead if you just want to do something when your stack is opened. On 2 Aug 2011, at 20:58, Pete wrote: > Not having any luck using the

Re: Startup message

Pete, The startUp message isn't sent to your stack if you open the stack in the IDE, nor if you open the stack while your standalone is already running. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twit

Re: Startup message anomaly?

Be careful with Parallels. Someone else (or maybe it was you) was saying that Parallels was returning unexpected path results. I believe it has something to do with Folder Redirection, a feature of Parallels which allows a user to redirect his windows profile and other folders to the Mac equival

Re: Startup message anomaly?

Thanks Jacque, I have now written a little app to test on both platforms, and you're right (of course). 'startUp' is sent initially to the first card, and if there's no handler there, or one which passes the message, it then reaches the stack. So the docs are wrong, and I will raise this. Howeve

Re: Startup message anomaly?

On 4/22/11 3:43 AM, Graham Samuel wrote: I've been taking the following description of the 'startup' message in the LS dictionary literally: Sent to the first stack opened when the application starts up. Well AFAIK the real case is that this is true for a Mac standalone but not in a Windows s