[messages] Edit: [Developers] Re: question about delete and order

Tim McCarron timothy.mccarron at sbcglobal.net
Wed Jul 28 15:07:28 MST 2010

No - I did answer your question.

What determines the order between Trait A and a Trait B on the same object
is its Stacking Order

Again, trait order work bottom up, as explained here

There is no other determining factor.
BUT there are exceptions and you've come across one

Namely, Triggers do not obey stack order and Report Actions do not obey
stack order. If the key that implements them is picked up by the keylistener
- they will execute - thats just how they work

There is no list. It's just something you learn building modules

-----Original Message-----
From: messages-bounces at vassalengine.org
[mailto:messages-bounces at vassalengine.org] On Behalf Of fil512
Sent: Wednesday, July 28, 2010 12:49 PM
To: messages at vassalengine.org
Subject: [messages] Edit: [Developers] Re: question about delete and order

[This message has been edited.]

Thanks tm.  It sounds like you don't know the answer to my question.  Is
there anyone else who lurks in these forums that knows the answer?  Once
again, my question is as follows.

What determines the order between a Delete and a TriggerAction on the
same object (possibly in different prototypes)? I am seeing a
ReportAction and GlobalKeyCommand both occurring before the Delete, but
the Trigger Action after the Delete. What determines the order that
traits fire?

Is there a list I can consult that shows the order?  Is it determined by
depth (i.e. would a chain of 3 triggers fire before a chain of 4
triggers)?  Is it determined by type (as seems to be the case
illustrated above)?  How can I determine the order?  I don't want to
just code *a* solution that works and leaves a big mess for the next
guy.  I want to code the "proper" solution.


Read this topic online here:
messages mailing list
messages at vassalengine.org

More information about the messages mailing list