Richard,
But in the last seven years I haven't written an app in which the
mainStack has more than one card;
That's interesting as that ability is one of the most
useful properties I've found in Rev. It's something
RealBasic flounders on. It has an object you can drop
on a Window that
On Feb 26, 2006, at 11:14 PM, Arthur Urban wrote:
Richard Gaskin wrote:
Arthur Urban wrote:
Is there a way I can detect when my main stack receives the
openStack message versus when my substacks receives the message
and pass it all the way down to the mainstack? I do once only
Is there a way I can detect when my main stack receives the openStack
message versus when my substacks receives the message and pass it all
the way down to the mainstack? I do once only initialization in my
mainstack, and I can't seem to reliably detect when a substack is
triggering the
Richard Gaskin wrote:
Arthur Urban wrote:
Is there a way I can detect when my main stack receives the openStack
message versus when my substacks receives the message and pass it all
the way down to the mainstack? I do once only initialization in my
mainstack, and I can't seem to reliably
Arthur Urban wrote:
Richard Gaskin wrote:
If you put your mainStack's initialization into the card script of
your mainStack you never need to worry about substacks triggering it.
That sure is mighty clever...I might even have to do that. I'm surprised
that there is no official and correct
on preOpenStack
if the short name of this stack = the short name of me then
-- do initialization
end if
end preOpenStack
Maybe this is the better way, because you can control the message even if
your main stack has more than one card.
Greetings
Paul Claude
