This could be a threading problem. Some movement of counters (e.g. Translate trait) occur on background threads, so the size of the Stack can change while CounterDetailViewer is examining it. It is probably just enough to check the iterated pieces still exist in the Stack before trying to select them for display.
some (most really) windows can grow quite large if you hog-wild with command keys for options, and there is no mechanism built into the windows to permit them to become scrollable. so at some point they push the keys to close them or edit them off the screen.
(specific example - restrict commands dialog - but there are at least a few others that have that potential - such as I believe the DP dialog if you add a lot of commands to it). Brent - I think we may have discussed this one very briefly already but I do not know if any decision was made how to approach it.
[this one could be a feature request rather than a bug per se but that depends how you look at it] when you cut and paste a piece (or probably most things?) then when you go to paste it again, there is no longer anything to paste. I believe the norm would be for you to be able to continue pasting the object just like if you had copied it rather than cut it?
vassalengine.org/forums/view … ight=#8388
This one never got any notice. It is minor and isolated enough that I actually mentioned it to Rodney also when I volunteered to try my hand as a part-time dev [crud, probably should, er, forget to mention that], but I have not done anything with it.
Those are the ones I know have been mentioned on the forum that might be actual bugs as opposed to feature requests.
This actually brings up another point. I know that I (well, most people really) should know how to report a bug against VASSAL on SourceForge.net , but should there not also be a link in a somewhat prominent spot on the vassalengine.org webpage (or in the about menu on the player and editor) for reporting bugs that do not come up because of the automatic bug reporter, with some statement of required info that should be given?
Right now I think the way that the vast majority of VASSAL users think they “report” a bug is simply to post it on the “Technical Support & Bugs” forum. But there is no guidance provided [okay it is there if you read the posts but it hardly slaps one in the face] in terms of what information is even basically needed (at least until some poor perplexed dev posts in response “What version of Vassal are you using?” “What steps did you take for this bug to occur?” “What version of Java are you running, and how do you find that out?” “What is your heap size set to for VASSAL and for Java and how much RAM is in your machine, and how do you figure all that out?” “What operating system are you using, and how do you figure that out ?” “How do we reach you for more info, and how do you figure that out :lol: ?” etcetera.
By 3.3 when all the bugs have gone away is too late to implement a user community bug reporting system!
Yes, we could do with a big Sticky message at the top of the Bug forum on ‘How to report a bug on this forum’
A lot of these questions are answered by information in the logfile. The big questions that don’t get answered by logfile are:
Who are you, how do we contact you. 50%+ of anonymous bug reports are useless because we cannot getmore info or follow up.
Where do I find a copy of the module.
How do you reproduce the problem.
Joel is planning to add a ‘Report a Vassal Bug’ option to the Module Manager which will act like the Auto-bug reporter and send the current logfile in. So you won’t have to wait for something to fail. If you see something wrong, you will be able to generate a new bug report. I’m not sure if this will make 3.1 though.
This fix worries me, because it’s only a bandage. That’s probably ok for
now, but we need to work out the underlying threading issue in the long
run. Separation into model and view would be a permanent solution to this