On Fri, Feb 6, 2015 at 12:33 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
If almost everything needs to use the open* handlers except one or two
stacks, then I put the handlers into the mainstack stack script and put
blocking handlers into the stacks that are an exception.
This.
I
Put the handlers in the card script of the main stack. When opening the
mainStack the card will receive the messages, but not when the substacks are
opened. The card of the mainStack is not in the message path of the substacks.
Alternately, you can put the same handlers in the substacks stack
There are some advantages to using substacks methinks. The monistic
automatically “knows” about the substacks without any extra coding or adding
the stacks to the main stack files property. Also, I am not sure that graphics
loaded in the main stack will be accessible to any stacks that are not
On 2/6/2015 1:38 PM, Bob Sneidar wrote:
Not sure but if you password protect the main stack, aren’t the
substacks inaccessible as well?
Nope. You have to protect each one separately.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software |
On 2/6/2015 12:49 AM, Brahmanathaswami wrote:
If you put any preopenstack, resizestack, close stack etc. script in the
mainstack script.. these will be triggered by the same action in a
substack.
What is the best way to avoid this?
I usually do the thing where you put the open* handlers into
it depends
got it... for me it's not about protecting anything..
it's about..eg.
on resizestack x,y
set the rect of some grc to the rect of this card
# and other tricks here relating to dynamic geometry changes...
end resize stack
This gets triggered by a substack that does not have
Brahmanathaswami wrote:
it depends
got it... for me it's not about protecting anything..
it's about..eg.
on resizestack x,y
set the rect of some grc to the rect of this card
# and other tricks here relating to dynamic geometry changes...
end resize stack
This gets triggered by a
Richard Gaskin wrote:
1) If the mainstack is a single card, just put the handler in the card
script.
2) If the mainstack has multiple cards, put the handler in a common
group script.
3) If neither of those are viable in your setup, you could add a check
to make sure the long name of me
Hi Brahmanathaswami,
It isn't obligatory to use substacks. You could use two mainstacks
simultaneously. Just make sure to include the additional mainstacks as
files when you build a standalone.
With two mainstacks, the scripts in one stack won't be triggered by
messages from the other. If
If you can do it, the easiest way is to place all your handlers in the card
script of the first card of your main stack. All the handlers will be
triggered by the main stack, but not the substacks.
If you must place your handlers in the stack script, you can compare the name
of the owner of
If you put any preopenstack, resizestack, close stack etc. script in the
mainstack script.. these will be triggered by the same action in a substack.
What is the best way to avoid this?
I just moved all those to the main background group of the main stack,
but I'm not happy with that
11 matches
Mail list logo
