Re: Accessing handler in LC resource stack

2016-02-07 Thread jameshale
Thanks Ali, > Ah ok, it just needs the ...of stack "revStandaloneSettings" removed then, Worked! > or should be changed to revSaveAsStandalone theStack, theOutputFolder Didn't work (tried it first :-)) -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Acces

Re: Accessing handler in LC resource stack

2016-02-07 Thread Ali Lloyd
Ah ok, it just needs the ...of stack "revStandaloneSettings" removed then, or should be changed to revSaveAsStandalone theStack, theOutputFolder On Mon, Feb 8, 2016 at 1:02 AM jameshale wrote: > Ali Lloyd-2 wrote > > revsaveasstandalone.livecodescript is just a stack named > > "revSaveAsStandalo

Re: Accessing handler in LC resource stack

2016-02-07 Thread jameshale
Ali Lloyd-2 wrote > revsaveasstandalone.livecodescript is just a stack named > "revSaveAsStandalone", so can be referred to that way, eg dispatch > "handler" to stack "revSaveAsStandalone". > > However, it *should* be in the backscripts already, so I think that may > not > be the problem (unless t

Re: Accessing handler in LC resource stack

2016-02-07 Thread Ali Lloyd
revsaveasstandalone.livecodescript is just a stack named "revSaveAsStandalone", so can be referred to that way, eg dispatch "handler" to stack "revSaveAsStandalone". However, it *should* be in the backscripts already, so I think that may not be the problem (unless the GLX framework explicitly call

Re: Accessing handler in LC resource stack

2016-02-07 Thread [-hh]
James H. wrote: > Hi, I am using the GLX framework with LC7 and have hit a snag. > Its application builder calls a handler in an LC resource stack > "revStandaloneSettings.rev" which no longer exists. Looking at > the LC package I think it has been replaced by > revsaveasstandalone.livecodescript