Just looked into that, but I am not using either one of those traits. My prototype(s) only use "report action" and "delete" traits. My pieces use "Basic Piece", "Prototype" and 1 "Layer" traits.
It seems to me though that the problems might be related, that somehow information about the border includes the outer bound (being the size of the window), and it is being ignored on the Windows JVM, but being taken into consideration by the Apple JVM. It might be interesting to find out if this issue also exists on the Linux JVM. --- In [email protected], Gary Krockover <[EMAIL PROTECTED]> > At 12:59 PM 12/8/2005, you wrote: > >Basically, instead of just drawing a frame around the currently > >selected piece, it also draws one around the inside of the window, > >you end up dragging around a giant flickering rectangle with every > >piece you move. Not a game killer, but still rather distracting. > > You might check the order of your traits- it sounds very much like the same issue that is reproducible on Windows machines; from the Wiki: > > "Why do I get large selection boxes when using Masks and Movement Trails? > > Because the Mask is being applied to the Movement Trails, which generate a bounding box to cover the entire trail. Moving the Mask trait above the Movement Trail trait on the trait list should cure this problem." ------------------------ 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/
