Hi James, >*********** REPLY SEPARATOR *********** > >On 4/07/2007 at 11:34 PM rindis8 wrote: >--- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> wrote: >> >> Hi James, >> >> 'Replace With' does just that, it replaces one piece completely with >another completely unrelated piece exactly as you have it defined in >the module. Vassal is doing exactly what it is supposed to - it >doesn't (and can't) "know" that the 'replace with' piece is actually >related to the old piece and needs to be manipulated in some way. > >Then what is the 'match current state' for? I figured it would try to >preserve such things as what layer was active.
Ok, yep, this should work, but has limits. Check that the setup of the traits that you want to match are identical in the two counters. ie. you cannot match the moved trait in one piece with another if they use different moved images, or have different offsets. To match a layer, the layer name, plus the names of all the layer images would have to be the same - which is unlikely in your case. >> You have two options: >> >> 1. Somehow communicate the 'state' of the old piece to the new >piece. This can be complicated - you need to use 'Place Marker', >rather than 'Replace', then use Global Key Commands on the old counter >to update the new counter, then delete the old counter. >> >> 2. Don't use 'Replace with' to change sides, implement the >'ownership' within the one piece. What makes a piece belong to one >side or the other - color? use a layer. Marker value? make it a >dynamic marker that can flip between the two sides. > >The problem with #2 is that I'm *already* using layers. There's six >different things and three different sides it could be at this point. >I can either have six different counters with three layers for the >different races, or I can have three counters (one for each race) that >each cycle through the six possible values. I don't see a real way to >do both at once. Not knowing your module, it is hard to comment, but combining both 'values' and 'sides' into a single counter would be the way to go. What about using images with transparent backgrounds for the 'six different things' that would overlay the fully opaque 'three different side' backgrounds? You could then cycle through both 'side' and 'value' in the one counter. >So, I guess at this point, my question is, if 'Match Current State' >isn't keeping track of moved/not moved status, and active layer >status, what *is* it keeping? The state of 'identical' traits in both counters. Regards, Brent. >James ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED]
