Page 1 of 1

What message come from "quit"

Posted: Sat Jun 14, 2014 12:39 am
by Simon
Hello everyone,
I'd like to know what messages follow closeCard during a quit. I need to process some final information.
We've got:
closeCard
shutDown
closeStack
closeStackRequest
probably others. I guess I want the order these messages (others) come in.
I caught a glimpse of closeStack but I'm guessing it's no place for a post command (I'm posting data) as the data never got posted.

Thanks for info.
Simon

Re: What message come from "quit"

Posted: Sat Jun 14, 2014 11:18 pm
by Mark
Hi Simon,

Have you tried shutDownRequest already?

Mark

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 2:05 am
by Simon
Hi Mark,
Thanks, I'll try that.
But now I'm interested in that actual order of messages after "quit". As I just found out (I Think) that preOpenCard may come before preOpenStack(?).
Wait...Am I crazy to think that the message path is Always active? If I have a button with "on preOpenStack answer "HELLO"" it will trigger before a card or stack script that says "on preOpenStack answer "Im a stack script""?

Simon

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 2:28 pm
by bn
Hi Simon,

From what I see in the message watcher it is:
preOpentStack
preOpenCard
openStack
openCard

And the receiver is the actual card and from there on the message passes through the message hierarchy.
If I have a button with "on preOpenStack answer "HELLO"" it will trigger before a card or stack script that says "on preOpenStack answer "Im a stack script""?
the button is not in the message path and it would not get "preOpenStack". When you press a button it starts a message path where the first receiver is the button and then on. (Not considering a front script)

Kind regards
Bernd

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 3:34 pm
by [-hh]
..........

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 9:10 pm
by Simon
Wow Hermann,
shutdownRequest Card 1402861353474
shutdownRequest Stack 1402861353477
shutDown Card 1402861353479
closeCard Card 1402861353479
closeStack Card 1402861353479
focusOut Card 1402861353480
Note the shutdownRequest Stack only works when using "quit" not the titlebar "X".

Now this was a very brute method of tracking messages, I couldn't figure out a way to record the messages watcher. Is there a way?

Thanks both of you.

Simon

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 9:40 pm
by FourthWorld
4W Flight Recorder (available through RevNet) offers more flexible options for tracking messages than the Message Watcher, with a more readable display.

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 9:49 pm
by Simon
Hi Richard,
When is RevNet going to return? It's still the Special Edition.

Simon

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 9:58 pm
by FourthWorld
Oops, my bad- yes, I need to post the new one ASAP (no one else had noticed and with my client work is just forgotten).

I'm the meantime, here's the direct link to that and more:
http://fourthworld.net/revnet/devolution/

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 11:05 pm
by [-hh]
..........

Re: What message come from "quit"

Posted: Sun Jun 15, 2014 11:25 pm
by Simon
Hi Hermann,
Yeah, that's is just about the way I did it.
I think I have my answer now. closeStack comes after closeCard but doesn't like to do anything. Maybe I had it set up wrong.

Simon

Re: What message come from "quit"

Posted: Mon Jun 16, 2014 12:02 am
by [-hh]
..........

Re: What message come from "quit"

Posted: Mon Jun 16, 2014 4:53 pm
by jacque
With very few exceptions, almost all engine messages are sent to the current card.

Re: What message come from "quit"

Posted: Mon Jun 16, 2014 8:52 pm
by [-hh]
..........

Re: What message come from "quit"

Posted: Tue Jun 17, 2014 4:45 pm
by jacque
All messages sent to the card will traverse the message hierarchy until they are intercepted. That includes all the pre- and open- messages.

The only messages I can think of offhand that don't go to the card are callback messages which are sent to a player control. (A script needs to set this up specifically.) It's noted in the dictionary. There may be others I can't think of right now, and that's why I was vague about it. ☺