Hi, Rodney, Thanks for this information. I have changed the properties to be as you suggested and the module is now working as expected. However... I have a module that was created pre-version 3.0 that uses this same trait and that module DOES have the offsets set to 2 and 4 and it works fine. Just thought I'd share that with you in case you wanted to see what caused this change in the new version.
Now, if you have the time, you can use this module (actually, I have uploaded a newer version of this module to the same module directory and called it "Rodney's new one") to research two other bugs. The first bug is the Mark Unmoved button that does not display the button text. The second bug is the button that doesn't become visible on a map window until the window is resized. To see the second bug, just start up a new game and open the Activation Markers window. When the window first opens there are no buttons visible. However, when the window is resized (by grabbing the window edges and then expanding the window) the button magically appears. Thanks. Kevin ----- Original Message ----- From: Rodney Kinney To: [email protected] Sent: Monday, October 01, 2007 1:26 AM Subject: Re: [vassalengine] Bug? Not sure... > Thanks for the reply. Unfortunately, neither option 1 (click away and > then click back) nor option 2 (change the user preference) works to correct > this. As I mentioned previously, the only way to make the new marker stack > with the original unit is to: The reason your marker is not stacking with the original unit is that you've specified a non-zero offset in the Place Marker properties. You can solve your problem by changing the vertical and horizontal offset to 0. VASSAL assumes that the marker shouldn't stack with the original unit if it's not placed in the exact same location. I've updated the Reference Manual to mention this. rk [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
