Thus far no one has been able to describe how to reproduce the problem
consistently. We NEED a way of reproducing this problem in order to solve it.
So far, we’ve had the following reports:
OS Java Mode Module Dragging From
-------------------------------------------------------------------
Win XP 1.6.0_05 Editor Cedar Mountain palette
Win XP 1.5.0_06 Editor VSQL palette
Win Vista 1.6.0_10-rc2 Editor Monsterpocalypse palette
Win XP 1.6.0_07 Editor Zombies!!! map
Vista 1.6.0_07 Editor France, 1940 map
Linux 1.6.0_0 Player Critical Collapse palette
Win 2k 1.6.0_07 Editor Federation & Empire palette
Win XP 1.6.0_07 Editor Warmachine palette
MacOS X 1.5.0_16 Editor Britannia palette
I see no clear pattern here, as we have at least one such report from each OS
we support, from both Java 5 and Java 6, from both the Player and the Editor,
from many different modules, and when dragging from both a map and a piece
palette.
If you can find a way to reliably reproduce this problem, PLEASE let us know
how.
Funny, since the last one I sent about Zombie!!! a few days ago, I haven’t had any problems whatsoever. It may have been something to do with some properties I had that were clashing somehow, but since I change them quite often, I don’t know what that could have been. And it’s not like it happened every time I did that specific movement, either. I could move a card to/from the window I was using 20-50 times before that error would come up. Maybe it also had to do with the image cache? If you like, I could go back in my module versions to see if I still have one that can reproduce it.
Well, looking back at the Bug Tracker, and the timing of the reports I made (which were a week ago today), I’d have to guess that that happened when I was using beta4. I can’t remember having any problems at all with beta5 in that department. Maybe you should consider adding VASSAL versions to the ABRs data to collect.