Re: startUp messaging hierarchy

2018-09-02 Thread Martin Koob via use-livecode
Hmm...  

Just looking at dictionary for widgets and it has an OnOpen message that is
sent to the widget when a card becomes the current card.  So I think that
message would be part of the startup messaging hierarchy  

Is that correct?

Martin


Martin via use-livecode wrote
> Hi
> 
> Your post made me curious.  I am sure I had seen this discussed in the
> forums with someone providing a good explanation but can't find it now
> either.
> 
> I did find this.
> 
> http://fourthworld.com/embassy/articles/revolution_message_path.html
> 
> That shows the extended message path with Behaviors & Libraries. I don't
> think that changes the messages that are sent at startUp. However if you
> had
> a /startUsing/ command  for a library stack during startup that stack
> would
> get a /libraryStack/ message.  I am pretty sure that behaviours don't 
> send
> any messages when the object they were the behaviour like a card or stack
> for was opened. I have no idea what widgets would do.
> 
> Hopefully someone will respond.
> 
> A good explanation of this would be a good thing to put in the
> documentation
> somewhere.
> 
> Martin
> 
> 
> 
> 
> FlexibleLearning.com via use-livecode wrote
>> I find myself unable to answer this rather basic question, and cannot
>> locate
>> any information...
>> 
>> e.g.
>> This is both incomplete and also most likely incorrect...
>> 
>> startUp (if engine is not already loaded)
>> - frontScript:
>> -- PreOpenStack
>> -- PreOpenCard
>> -- openStack
>> -- openCard
>> -- preOpenBackGround
>> -- openBackground
>> 
>> preOpenStack
>> preOpenCard
>> openStack
>> openCard
>> preOpenBackground (if closed)
>> openBackground (if closed)
>> 
>> - backscript:
>> -- PreOpenStack
>> -- PreOpenCard
>> -- openStack
>> -- openCard
>> -- preOpenBackGround
>> -- openBackground
>> 
>> Anyone?
>> 
>> Hugh
>> 
>> 
>> ___
>> use-livecode mailing list
> 
>> use-livecode@.runrev
> 
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> 
> 
> 
> --
> Sent from:
> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
> 
> ___
> use-livecode mailing list

> use-livecode@.runrev

> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: startUp messaging hierarchy

2018-09-02 Thread Martin Koob via use-livecode
Hi

Your post made me curious.  I am sure I had seen this discussed in the
forums with someone providing a good explanation but can't find it now
either.

I did find this.

http://fourthworld.com/embassy/articles/revolution_message_path.html

That shows the extended message path with Behaviors & Libraries. I don't
think that changes the messages that are sent at startUp. However if you had
a /startUsing/ command  for a library stack during startup that stack would
get a /libraryStack/ message.  I am pretty sure that behaviours don't  send
any messages when the object they were the behaviour like a card or stack
for was opened. I have no idea what widgets would do.

Hopefully someone will respond.

A good explanation of this would be a good thing to put in the documentation
somewhere.

Martin




FlexibleLearning.com via use-livecode wrote
> I find myself unable to answer this rather basic question, and cannot
> locate
> any information...
> 
> e.g.
> This is both incomplete and also most likely incorrect...
> 
> startUp (if engine is not already loaded)
> - frontScript:
> -- PreOpenStack
> -- PreOpenCard
> -- openStack
> -- openCard
> -- preOpenBackGround
> -- openBackground
> 
> preOpenStack
> preOpenCard
> openStack
> openCard
> preOpenBackground (if closed)
> openBackground (if closed)
> 
> - backscript:
> -- PreOpenStack
> -- PreOpenCard
> -- openStack
> -- openCard
> -- preOpenBackGround
> -- openBackground
> 
> Anyone?
> 
> Hugh
> 
> 
> ___
> use-livecode mailing list

> use-livecode@.runrev

> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


startUp messaging hierarchy

2018-09-01 Thread FlexibleLearning.com via use-livecode
I find myself unable to answer this rather basic question, and cannot locate
any information...

e.g.
This is both incomplete and also most likely incorrect...

startUp (if engine is not already loaded)
- frontScript:
-- PreOpenStack
-- PreOpenCard
-- openStack
-- openCard
-- preOpenBackGround
-- openBackground

preOpenStack
preOpenCard
openStack
openCard
preOpenBackground (if closed)
openBackground (if closed)

- backscript:
-- PreOpenStack
-- PreOpenCard
-- openStack
-- openCard
-- preOpenBackGround
-- openBackground

Anyone?

Hugh


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode