There also appears to be a bug in the way the movement trail is drawn when using the keyboard keys. When using the mouse to move the game piece, they movement trail is drawn BENEATH the game piece. However, when you use the keyboard keys to move the gam piece, the movement trail is drawn ABOVE the game piece partially obscuring it.
--- In [email protected], Brent Easton <[EMAIL PROTECTED]> wrote: > > Hi Rodney, > > I had a quick look, but am passing this one over to you as 'Move fixed > distance' uses a MoveExecuter and I think the problem is tied up with > the asynchronous movement. > > The first 'Move fixed distance' after a manual move does not generate a > Movement Trail point, subsequent 'Move fixed distance' commands do. If > you then move the piece manually again, the next 'Move fixed distance' > again does not generate a movement trail point. > > For Movement trail to work, Footprint needs setProperty(MOVED) called > after it the piece has moved, I suspect it is being called before. > > Regards, > Brent. > > skorpio2011 wrote: > > > When I use Move predefined distance, in my V Battlefleet Gothic > > module, the movement trail appears only when I move a ship twice or > > more. The first part of the trail is always invisible. However, there > > is no problem when I move a ship by hand. > > This error occurs since I updated Vassal from 2.0.5 to 2.4.2. > > > > Regards, > > Skorpio > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/IMSolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/vassalengine/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
