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
second stack tries to open it's "splash", LC simply goes to the "splash"
the first stack already has open.
The only conflict warning I got was when I set the stackfiles of stack "test1"
to one copy of "splash", then attempted to do the same thing
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 stac
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 abl
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 yiel
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
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 wil
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 i
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, th
ot;
In memory or not, you can refer to a stack by its filename:
get the width of btn 1 of stack "/home/klaus/MyStack.livecode"
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.
--
Richa
t like the stack xyz scripts?
>
> If I understand you, then another stack can reference the stackfiles of xyz
> by getting the stackfiles of stack xyz.
Ok, that my be one solution to my questions.
> But I cannot think that is what you meant. The stackfiles is a property of a
> singl
> 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
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 anothe
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.
I
yes, I know, this way it also lets other stacks us the "used" stacks external
etc, but does this apply to STACKFILES, too?
That was my question!
> Bob S
>
>> On Aug 9, 2018, at 02:58 , Klaus major-k via use-livecode
>> wrote:
>>
>> Hi friends,
>>
,
>
> quick question:
> When I "start using stack xyz" then all stack can access the scripts etc.
> of stack xyz. Does this also apply to the stackfiles of stack xyz?
>
> Thanks in advance!
>
>
> Best
>
> Klaus
> -
Hi friends,
quick question:
When I "start using stack xyz" then all stack can access the scripts etc.
of stack xyz. Does this also apply to the stackfiles of stack xyz?
Thanks in advance!
Best
Klaus
--
Klaus Major
http://www.major-k.de
kl...@
be
>
> becomes
>
> lib_calendary
> /users/brahma/documents/myapp/libraries/lib_calendar.livecodescript
>
> plus you are changing files from time to time, so the stackfiles is obsolete.
>
> We fixed this by starting w
Do you mean you store the stackfiles in a database, then load the locations
with the splash screen?
Bill
> On Mar 27, 2018, at 2:52 PM, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> You the splash get "messed-up" from occasional resave.
>
> Don't
myapp/libraries/lib_calendar.livecodescript
plus you are changing files from time to time, so the stackfiles is obsolete.
We fixed this by starting with json files, which then sets the splash
stackFiles on stack start up
On 3/27/18, 11:13 AM, "use-livecode on behalf of William Prothero via
k. I am using “the
> stackfiles” of the splash stack to get the relative paths of the various
> stacks in the resources folder. I’m on LC 9.0.0(rc2), on Mac OS 10.12.3
>
> What I’m wondering is if there are any “gotchas” with using this method to
> get the relative paths to the
Folks:
I’m setting up an application with a splash stack and lots of other stacks and
libraries that are loaded by the splash stack. I am using “the stackfiles” of
the splash stack to get the relative paths of the various stacks in the
resources folder. I’m on LC 9.0.0(rc2), on Mac OS 10.12.3
Added a "Save StackFiles" menu item to the popup menu when right-clicking
on a stack or multiple stacks. This is especially useful for stacks using
script-only behaviors. With one command it saves all the stacks referenced
in the stack's stackfiles property. This is particularly us
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, bu
> 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
cr& \
>> "game2,game2.rev"& cr& & cr& "animationEngine,**animationEngine.rev"
>> \
>> into tStackFiles
>> set the stackFiles of stack "Mainstack.exe" to tStackFiles
>> ...
>> open stack "Index-stack&q
t;& cr& \
"game2,game2.rev"& cr& & cr& "animationEngine,animationEngine.rev" \
into tStackFiles
set the stackFiles of stack "Mainstack.exe" to tStackFiles
...
open stack "Index-stack"
hide stack "Mainstack"
end setUpF
Hello,
Apologies for the length of this, but I'd very much like list help to
understand better a scripting practice I've been doing half-baked for
a long time now.
It has to do with stackFiles (I think?), the steps for implementing
which I describe below, but first precede with an
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
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 beha
e:
>
>> 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 m
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 worki
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 behavior scripts. The buttons
that hold the b
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 refe
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&#
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
> 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
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
>> 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
other stacks
that I refer to for various reasons from my application.
The intent of all this is to have a library of reusable code available to any
and all applications I write. I was given the stackfiles methodology some time
ago by someone on this list, but perhaps it's not the best w
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
> 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
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 stack
48 matches
Mail list logo
