Create account / Log in

Trigger properties don't match with current and old maps

Issues with the Vassal engine.

Moderators: uckelman, Tim M

Trigger properties don't match with current and old maps

Postby LB » September 30th, 2012, 4:42 am

G'day,

In my module, I have set all the map windows to fire an "alt W" combo each time a piece ends it's movement on a map.

In a trigger on a card, I have set it to fire a report every time "alt W" is detected, i.e. when this card gets dragged around from one map to another. The property match I have specified is $CurrentMap$ != $OldMap$. However, when I move the piece around within the same window, the trigger still fires. So even though CurrentMap and OldMap are the same, the trigger fires. I have placed a text label on the card to check what the properties $CurrentMap$ and $OldMap$ are and it reports that they are the same.

I am using Vassal 3.2 beta 3 and have entered this as bug 4836.

Cheers

LB
LB
 
Posts: 60
Joined: July 23rd, 2010, 5:01 am

Re: Trigger properties don't match with current and old maps

Postby barbanera » October 1st, 2012, 1:46 pm

The correct syntax is:

CurrentMap != $OldMap$
barbanera
 
Posts: 384
Joined: January 12th, 2012, 2:27 pm

Re: Trigger properties don't match with current and old maps

Postby LB » October 1st, 2012, 1:56 pm

Cheers.

Thanks for that.
LB
 
Posts: 60
Joined: July 23rd, 2010, 5:01 am

Re: Trigger properties don't match with current and old maps

Postby barbanera » October 1st, 2012, 2:19 pm

If that fixed your problem then maybe you should remove the bug report now :-)
barbanera
 
Posts: 384
Joined: January 12th, 2012, 2:27 pm

Re: Trigger properties don't match with current and old maps

Postby LB » October 2nd, 2012, 9:59 am

Done.
LB
 
Posts: 60
Joined: July 23rd, 2010, 5:01 am


Return to Technical Support & Bugs

Who is online

Users browsing this forum: Google [Bot] and 6 guests