Re: Getting Library Stacks into Memory

2016-07-14 Thread Sannyasin Brahmanathaswami
Forget it… too long a day.. .I needed another segment my path… sorry for the noise Amazing how hard this is for me… I must be super dense or something is really missing in the docs. OK , so you say we don't need to use "go" to get stacks into memory I have this in my loader stack put ( get

Re: Getting Library Stacks into Memory

2016-07-14 Thread Sannyasin Brahmanathaswami
Amazing how hard this is for me… I must be super dense or something is really missing in the docs. OK , so you say we don't need to use "go" to get stacks into memory I have this in my loader stack put ( getPathForSharedLibraries() & "itemMetadataParser.livecodescript") into tMediaParser put

Re: Getting Library Stacks into Memory

2016-07-09 Thread Dar Scott
But LiveCode is not C. In LiveCode an array is a value, not a special kind of variable. put "abcd" into cup 1 of that egg carton in the box labeled "alphabetBlocks" (I know, Dar sees the world funny.) > On Jul 9, 2016, at 1:20 PM, Richard Gaskin wrote: > > J. Landman Gay wrote: >

Re: Getting Library Stacks into Memory

2016-07-09 Thread Richard Gaskin
J. Landman Gay wrote: > On 7/9/2016 1:39 PM, Richard Gaskin wrote: >> After all, how does one express an array in English? :) > > "Egg carton". Devin taught me that while brandishing a prop at one of > our teaching sessions. > >put "abcd" into cup 1 of eggcarton "alphabetBlocks" Conceptually

Re: Getting Library Stacks into Memory

2016-07-09 Thread [-hh]
ext: http://runtime-revolution.278305.n4.nabble.com/Getting-Library-Stacks-into-Memory-tp4706461p4706515.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url

Re: Getting Library Stacks into Memory

2016-07-09 Thread J. Landman Gay
On 7/9/2016 1:39 PM, Richard Gaskin wrote: After all, how does one express an array in English? :) "Egg carton". Devin taught me that while brandishing a prop at one of our teaching sessions. put "abcd" into cup 1 of eggcarton "alphabetBlocks" At first I thought it was some kind of yolk b

Re: Getting Library Stacks into Memory

2016-07-09 Thread Richard Gaskin
Mark Wieder wrote: > On 07/09/2016 10:13 AM, Richard Gaskin wrote: > >> One might even say it becomes the "parent script" of the control. >> >> If only we had a word to describe that unique role clearly... ;) > > Ah... the problems of trying to set up a one-to-one correspondence > between techni

Re: Getting Library Stacks into Memory

2016-07-09 Thread Mark Wieder
On 07/09/2016 10:13 AM, Richard Gaskin wrote: One might even say it becomes the "parent script" of the control. If only we had a word to describe that unique role clearly... ;) Ah... the problems of trying to set up a one-to-one correspondence between technical terms and natural language. I

Re: Getting Library Stacks into Memory

2016-07-09 Thread Richard Gaskin
Mark Wieder wrote: > On 07/08/2016 10:57 PM, J. Landman Gay wrote: >> I seem to remember inserting the script of a stack into back at some >> point in the past. > > Probably also worth pointing out here that if you assign a behavior > to a control, the behavior acts as a backscript to that contro

Re: Getting Library Stacks into Memory

2016-07-09 Thread Mark Wieder
On 07/08/2016 10:57 PM, J. Landman Gay wrote: I seem to remember inserting the script of a stack into back at some point in the past. Probably also worth pointing out here that if you assign a behavior to a control, the behavior acts as a backscript to that control. -- Mark Wieder ahsoftw.

Re: Getting Library Stacks into Memory

2016-07-08 Thread J. Landman Gay
I seem to remember inserting the script of a stack into back at some point in the past. I know for sure you can start using the stack which is effectively the same thing. The main thing is that you don't need to "go" there to load the stack into RAM. Just putting it in use does that, as does a

Re: Getting Library Stacks into Memory

2016-07-08 Thread Mark Wieder
On 07/08/2016 12:48 AM, J. Landman Gay wrote: insert the script of the stack into front or back Now *that* would be an interesting addition to the language "...surprise me, Trebek..." -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing

Re: Getting Library Stacks into Memory

2016-07-08 Thread Sannyasin Brahmanathaswami
Jacque wrote: "insert the script of the stack into front or back" The dictionary implies that this can only be done with an "object" , hence the assumption (probably wrong) that one needs to have the stack open… I assume you mean that we can do it like this now with script only stacks insert

Re: Getting Library Stacks into Memory

2016-07-08 Thread Sannyasin Brahmanathaswami
t all the go invisible commands on start up are still breaking the loading. We'll fix that today Swasti Astu! Be Well ( from my mobile ) _ From: J. Landman Gay mailto:jac...@hyperactivesw.com>> Sent: Thursday, July 7, 2016 9:48 PM Subject: Re: Getting Lib

Re: Getting Library Stacks into Memory

2016-07-08 Thread J. Landman Gay
These almost sound like undefined errors with the group name as the object hint. Mobile apps can only have one window at a time, and each "go" replaces the previous window. If you go to an invisible stack you'll see black. In general don't use "go" for that kind of thing, just using the stack

Getting Library Stacks into Memory

2016-07-07 Thread Sannyasin Brahmanathaswami
Our new app was loading nicely on the iPhone.. .we externalized a lot of code to scripts that are meant to be used in front, back and as behaviors… with the go stack cmd logInfo "Loading frontscript" && tStackPath go stack (getPathForSharedLibraries() & tStackPath) insert the script of stack