Hypercard to Studio conversion

Gordon Shimizu gshimizu at santarosa.edu
Wed Oct 4 12:31:40 CDT 2006


Thanks for this.
My main directory stack contain buttons that opens other stacks. I placed
the close stack command in one of the button and it did close this main
directory stack.  However, it did not open the stack that this button should
have been linked to.  I used openStack and file name of the stack I wanted
to open with this button but nothing happened.  I think I am missing the
pathway to this stack I want to open.  Can you help?
Thanks.

On 10/3/06 10:17 PM, "Mark Swindell" <mdswindell at cruzio.com> wrote:

> close command
> 
> Platform support:
> Introduced in version 1.0
> 
> Closes a stack window.
> 
> close stack
> 
> close stack "Fearsome Stack"
> close the defaultStack
> 
> See also: close file command, close printing command, close process
> command, close socket command, destroyStack property, go command,
> revCloseVideoGrabber command, How do I open and close a drawer?, How
> do I respond to closing a window?
> 
> Description
> Use the close command to close a stack without user intervention.
> 
> Parameters:
> The stack is any open stack.
> 
> Comments:
> The close command closes the stack window immediately, but it does
> not necessarily remove the stack from memory. A stack that is closed
> but in memory still takes up space in RAM and its objects are still
> accessible to scripts.
> 
> If the stack's destroyStack property is set to false, or there are
> other stacks in the same file that are still open, closing the stack
> does not purge the stack from memory.
> 
> If the handler that closes the stack is in the script of the stack
> (or in the script of an object in the stack) and the stack's
> destroyStack property is true, the stack window is closed
> immediately, but the stack is not removed from memory until after the
> handler completes.
> 
> 
> Mark
> 
> On Oct 3, 2006, at 4:25 PM, Gordon Shimizu wrote:
> 
>> I'm in the process on converting a number of my hypercard stacks into
>> Studio.  I find Studio handlers very similar to hypercard's.
>> However, the
>> converted stacks do not behave as in hypercard (didn't expect it to!).
>> My converted stacks consist of a master directory stack that was
>> linked to a
>> subdirectory stack then to the individual topic stacks.  In
>> hypercard, when
>> I opened the master directory stack to open the subdirectory stack the
>> master directory stack would simply close.  In studio, the master
>> directory
>> stack window is still open and behind the subdirectory window.  How
>> can I
>> get the master directory to close as well as any stacks that is
>> opened from
>> the subdirectory stack?
>> 
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 




More information about the use-livecode mailing list