storing a stack as a customprop

Brian Yennie briany at qldlearning.com
Sat Oct 17 21:07:20 EDT 2009


Peter,

Are you sure you are including the "URL" keyword?

RIGHT:
set the storedStack of stack "updateList" to URL ("binfile:"&filepath)

WRONG:
set the storedStack of stack "updateList" to ("binfile:"&filepath)

> "binfile" instead of "file" doesn't change things. Still don't get  
> the actual stack into the property, just the filepath.
>
> ???
>
> Could it be that the stack hasn't finished saving to disk before I'm  
> trying to fetch it from the disk to get it into the property? Do I  
> have to do a wait with messages or something?
>
> -- Peter
>
> Peter M. Brigham
> pmbrig at gmail.com
> http://home.comcast.net/~pmbrig
>
>
>
> On Oct 17, 2009, at 8:22 PM, Mark Schonewille wrote:
>
>> Peter,
>>
>> Use binfile instead of file.
>>
>> set the storedStack of stack "updateList" to URL "binfile:" &  
>> filepath
>>
>> --
>> Best regards,
>>
>> Mark Schonewille
>
>
>>> I'm stuck. I swear I got this to work for a few minutes and now it  
>>> isn't working. I changed something and broke it.
>>>
>>> I'm trying to store a stack ("stackToSave") as a customproperty of  
>>> a stack called "updateList". As far as I can tell the way to store  
>>> a currently open stack in a property is to first save it to disk  
>>> and use something like
>>>
>>> set the storedStack of stack "updateList" to URL "file:" & filepath
>>>
>>> First question: is this the way to approach this task?
>>>
>>> If so, then a few more details: the stack "stackToSave" is a  
>>> substack of a stack "myMainStack" currently open in the IDE (all  
>>> of this is taking place in the IDE). The stack "updateList" is not  
>>> part of the same stackfile. I'm thinking I have to clone the stack  
>>> "stackToSave" first so I can save it independently. Second  
>>> question: is this true?
>>>
>>> I have a script in the stack "updateList" that calls a handler  
>>> "storeStack":
>>>
>>> ...
>>> put "stackToSave" into stName
>>> storeStack stName



More information about the use-livecode mailing list