I believe he is referring to the bug that we discussed shortly after version 2.9.9 was released. If you have a piece with the 'Movement Trail' trait, but that does not have the 'Mark When Moved' trait, then the global "Mark Not Moved" key will not clear the movement trails under v2.9.9.
The workaround is to add the 'Mark When Moved' trait to the piece definition without any graphic, so the piece is not visibly marked when moved, but the movement trails will then clear with the global key. It works, but it means you have to update all the pieces in your pre-set or saved games, which I imagine is why Kevin was hoping this would be fixed soon. Regards, Bill Bennett --- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> wrote: > > Hi Kevin, > > Which bug was this exactly? > > The Movement Trail is cleared whenever a counter is marked 'not moved'. This can be done using the global 'Mark not moved' key, or by adding a 'Mark Moved' trait with no command and triggering it directly. > > I can see the sense in having an additional key command to clear the movement trails independently of the mark moved status. > > Regards, > Brent. > > >On 8/04/2007 at 6:02 PM Kevin Coombs wrote: > >Does anyone know if a fix to the movement trail bug (where the trail > >cannot be removed) will be included in the next VASSAL release? If not, > >I'll have to change my existing modules to include the "workaround" to > >account for this bug (I've been putting off including the workaround > >hoping instead that the bug would be fixed soon). > > > >Thanks. > > > >Kevin > > ____________________________________________________________ > Brent Easton > Analyst/Programmer > University of Western Sydney > Email: [EMAIL PROTECTED] >
