Bob Sneidar wrote:
>> On Aug 9, 2018, at 15:51 , Richard Gaskin wrote:
>>
>> Besides, even if you had two stacks whose stackFiles had the same
>> stack short name assigned to different stackFiles, one of them
>> wouldn't work anyway because as soon as it tried you'd get a stack
>> name conflict w
Hi Richard.
I tested this. You don't get a conflict warning if the second stack attempts to
open it's version of "splash" after the first stack had opened it's version.
Instead, when the first stack has it's version of "splash" already opened, and
the second stack tries to open it's "splash",
Bob Sneidar wrote:
> On Aug 9, 2018, at 11:45 , Richard Gaskin wrote:
> Yes, the stackFiles property is every bit as global as any other use
> of stack names.
>
> Not to belabor the point, but the stackfiles is a property of a STACK,
> not a global system property.
A stack's name is also a prope
Not to belabor the point, but the stackfiles is a property of a STACK, not a
global system property. It would be like setting the foo of stack "test1" to
the filename of stack "splash", quitting LC, relaunching LC, opening stack
"test1", then expecting to be able to open stack "splash" using it'
Bob Sneidar wrote:
> How odd though. The stackfiles is acting like a global property.
> Imagine I have 2 projects open, each referencing 2 different versions
> of the same stack in different locations on the disk. Any attempt to
> open that stack using it's short name might yield the wrong stack.
Should be:
open stack tFullStackPath
> On Aug 9, 2018, at 09:23 , Bob Sneidar via use-livecode
> wrote:
>
> open tFullStackPath
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage y
The safe way then to do this would be:
put the stackfiles of stack "test1" into tStackFiles -- or whatever your stack
is named
filter lines of tStackFiles with "splash*" -- or whatever your stack short name
is
put item 2 of tStackFiles into tFullStackPath
open tFullStackPath
Bob S
> On Aug 9,
How odd though. The stackfiles is acting like a global property. Imagine I have
2 projects open, each referencing 2 different versions of the same stack in
different locations on the disk. Any attempt to open that stack using it's
short name might yield the wrong stack.
I know you will say: "W
Ah! I get it now.
I tested this. 2 stacks, one with the stackfiles set to a third stack somewhere
on disk. Second one with a button that opens the stack listed in the stackfiles
of the first stack using it's short name.
With both stacks open, Clicking the button opens the stack listed in the
Hi Richard,
> Am 09.08.2018 um 17:20 schrieb Richard Gaskin via use-livecode
> :
>
> Klaus major-k wrote:
> ...
> When a stack file is included among the stackfiles property of an open stack,
> you should be able to address it by short name if you like.
thank you, that finally answers my quest
Klaus major-k wrote:
> I mean if stack xyz has its stackfile property set, can other stack
> access this property just like the stack xyz scripts?
Every property of every object in every stack on your hard drive is
available to every script.
An object does no need to be loaded into memory to
Hi Bob,
> Am 09.08.2018 um 17:15 schrieb Bob Sneidar via use-livecode
> :
>
>> On Aug 9, 2018, at 08:07 , Klaus major-k via use-livecode
>> wrote:
>>
>> I mean if stack xyz has its stackfile property set, can other stack access
>> this property just like the stack xyz scripts?
>
> If I unde
> On Aug 9, 2018, at 08:07 , Klaus major-k via use-livecode
> wrote:
>
> I mean if stack xyz has its stackfile property set, can other stack access
> this property just like the stack xyz scripts?
If I understand you, then another stack can reference the stackfiles of xyz by
getting the st
Hi Bob,
> Am 09.08.2018 um 17:03 schrieb Bob Sneidar via use-livecode
> :
>
> I see, you are asking if the scripts of the stackfiles are inserted into the
> message heirarchy? No. It can't work that way if you think about it. You
> would never be able to include another stack in a standalone w
I see, you are asking if the scripts of the stackfiles are inserted into the
message heirarchy? No. It can't work that way if you think about it. You would
never be able to include another stack in a standalone without having every
stack script of every stack in the message heirarchy.
If you a
Hi Bob,
> Am 09.08.2018 um 16:48 schrieb Bob Sneidar via use-livecode
> :
>
> Start Using simply inserts the script of that stack in the back, so it is now
> in the message path which
> is global to everything running in that instance of livecode or the
> standalone.
yes, I know, this way it
Start Using simply inserts the script of that stack in the back, so it is now
in the message path which is global to everything running in that instance of
livecode or the standalone.
Bob S
> On Aug 9, 2018, at 02:58 , Klaus major-k via use-livecode
> wrote:
>
> Hi friends,
>
> quick ques
Hi Nicolas,
Coming late to the party... For an example of what 'the stackfiles' look like,
open the IDE message box and type"
put the stackfiles of stack "home"
Phil Davis
On 7/24/11 7:42 PM, Nicolas Cueto wrote:
Hello,
Apologies for the length of this, but I'd very much like list hel
> Although in this case, the stack in
> question is the main standalone stack, so it's always in use anyway.
Interesting (and come to think of it, obvious).
So does this mean that I do not need to include a "start using this
stack" in my standalone to allow other stacks to call functions and
han
On 7/25/11 1:43 PM, Pete Haworth wrote:
I think I missed the original post of this thread, but perhaps a "start
using" command would take care of all this?
If the stackfiles property is included in the inheritance hierarchy,
which is what I'm not sure of, then yes. Although in this case, the
I think I missed the original post of this thread, but perhaps a "start
using" command would take care of all this?
Pete
On Mon, Jul 25, 2011 at 11:28 AM, J. Landman Gay
wrote:
> On 7/24/11 9:42 PM, Nicolas Cueto wrote:
>
>
>> To do the above, here are my steps:
>>
>> STEP 1) place the follow
On 7/24/11 9:42 PM, Nicolas Cueto wrote:
To do the above, here are my steps:
STEP 1) place the following script in card 1 of AllMightyStack.exe:
on openCard
setUpFoundation
end openCard
on setUpFoundation
put "Index-stack,Index-stack.rev"& cr& "game1,game1.rev"& cr& \
"game2,game2.rev"&
Monte, Thanks for the update. I just changed all my code back to using the
stackFiles property instead of using the code you suggested in the Startup
event and now everything works! I have changed this code so many times now
that I honestly can't remember what is different about it now that wh
On Feb 14, 2011, at 3:01 PM, Peter Haworth wrote:
The behaviors are specified in the form "button id 1234 of stack
"xyzSub". I tried adding "of stack "xyz" after the behavior
specifications but the IDE simply removes that text.
Behavior references have to be in the form of a long id:
s
>>> However, it looks like I have some wholesale changes to make to get my
>>> stackFiles working correctly with regard to my behavior scripts. The
>>> buttons that hold the behavior scripts are in a substack. I've included
>>> the name of the behaviors substack and it's main stack in the stac
Thanks Monte, I'll give all of that a whirl.
Pete Haworth
http://www.mollysrevenge.com
http://www.sonicbids.com/MollysRevenge
http://www.myspace.com/mollysrevengeband
On Feb 14, 2011, at 1:59 PM, Monte Goulding wrote:
>
> On 15/02/2011, at 7:01 AM, Peter Haworth wrote:
>
>> My fr
On 15/02/2011, at 7:01 AM, Peter Haworth wrote:
> My front scripts are now working OK after I addedd "of stack "xyz" to my
> insert commands as Jacqueline suggested.
>
> However, it looks like I have some wholesale changes to make to get my
> stackFiles working correctly with regard to my beha
Thanks to all for the pointers and advice. I can get this working now with one
of the suggested methods or possibly a combination.
As for the issue of the mainstack not being in the behavior ID, I'm glad it's
not there, like Monte and wouldn't like to see the software changed to be in
line wit
Monte-
Sunday, February 13, 2011, 9:05:23 PM, you wrote:
> I personally like the idea that the behavior doesn't include the
> mainstack name so I can copy the substacks I store my behaviors on
> out of my object library into the standalone at build time without
> anything breaking ;-)
! I never
Monte Goulding wrote:
On 14/02/2011, at 3:43 PM, Mark Wieder wrote:
Monte-
Sunday, February 13, 2011, 7:49:38 PM, you wrote:
I believe you will have to add the substack with the behavior
buttons on it to the stackfiles too because the behavior rugged id
doesn't include a mainstack reference.
On 14/02/2011, at 3:43 PM, Mark Wieder wrote:
> Monte-
>
> Sunday, February 13, 2011, 7:49:38 PM, you wrote:
>
>> I believe you will have to add the substack with the behavior
>> buttons on it to the stackfiles too because the behavior rugged id
>> doesn't include a mainstack reference.
>
> Ur
Monte-
Sunday, February 13, 2011, 7:49:38 PM, you wrote:
> I believe you will have to add the substack with the behavior
> buttons on it to the stackfiles too because the behavior rugged id
> doesn't include a mainstack reference.
Urk. That's quite a gotcha. Is there a bug filed against this?
-
> Pete, if you want to use stackfiles, you can make do with the single entry
> you created that points to the mainstack. Then in your scripts, refer to the
> substacks as "stack mySub of stack xyz".
I believe you will have to add the substack with the behavior buttons on it to
the stackfiles to
On 2/13/11 9:17 PM, Mark Wieder wrote:
Pete-
Sunday, February 13, 2011, 6:49:41 PM, you wrote:
Need some clarification on the use of the stackFiles property. I
have a file, xzy.livecode. It has a mainstack and several
substacks. I need access to the mainstack and some of the substacks
in my
>> Need some clarification on the use of the stackFiles property. I
>> have a file, xzy.livecode. It has a mainstack and several
>> substacks. I need access to the mainstack and some of the substacks
>> in my application. I set up a stackFiles entry referring to the main
>> stack with a path to
Thanks Monte and Mark. The first thing I need to do is insert the scripts of a
couple of button in one of the substacks as front scripts. In the same
substack, I have a bunch of buttons whose scripts are referred to as behaviors
from controls within my application. There are also a couple of
Pete-
Sunday, February 13, 2011, 6:49:41 PM, you wrote:
> Need some clarification on the use of the stackFiles property. I
> have a file, xzy.livecode. It has a mainstack and several
> substacks. I need access to the mainstack and some of the substacks
> in my application. I set up a stackFile
> Need some clarification on the use of the stackFiles property. I have a
> file, xzy.livecode. It has a mainstack and several substacks. I need access
> to the mainstack and some of the substacks in my application. I set up a
> stackFiles entry referring to the main stack with a path to the
38 matches
Mail list logo
