Andrew,
Make the sub-stack a "palette" stack. Open the sub-stack via the command
palette "my substack.mc"
You can also set the style of an already opened stack via the command
set the style of wd "my substack" to palette
As far as not allowing the stack to be closed, one way would be to get rid
of the close box but I think the only way to do that is to get rid of the
title bar with the command
set the decorations of wd "my substack" to empty
Another approach might be to set up a handler for the closeStackRequest
message in the substack. (Warning: I just came up with this code as I typed
it. It hasn't been tested.)
on closeStackRequest
# If you don't want to allow the stack to be closed
# just make sure you don't "pass" the message on.
# See the help index for the closeStackRequest message
# You may want to check a global flag that is set by your
# close button and have the close button attempt to close
# the substack via the command
# close stack "my substack"
global allowClose
if allowClose then
pass closeStackRequest
end if
end closeStackRequest
Because you handled this message and didn't let it get back to MC then the
stack won't be closed even though the user clicked on the close box. Only
if the close box were clicked would the stack actually be closed.
I hope this points you in the direction you want to go.
Larry
>
> Okay, I'm not sure how I can do this. I have one main
> stack open then I open another smaller sub-stack above
> it (so you can still see the main stack). What I need
> is some way to make it so the user can only do things
> in the smaller stack and cannot close that stack
> unless they push a button labeled "close". If you
> click on the main stack the smaller sub-stack drops
> back behind the main stack, so the smaller stack also
> has to remain as the toplevel stack.
>
> Any ideas?
>
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
