# improved Bug Dialog demo (for beta4) **URL:** \ **Category:** Development\ **Created:** [October 13, 2008, 10:59pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102 "2008-10-13T22:59:55Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [October 13, 2008, 10:59pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/1 "2008-10-13T22:59:55Z")
Here’s a demo for the improved Bug Dialog I’ve been working on: [nomic.net/~uckelman/tmp/vass … ogTest.zip](http://www.nomic.net/~uckelman/tmp/vassal/BugDialogTest.zip) There are a shell script and a batch file in the archive from which you can run the demo. What you’ll see are three paths through the Bug Dialog, one where we want bug reports from your version of VASSAL, one where we don’t want bug reports, and one where the bug report check fails. Comments welcome. I’d like to include this in beta4 (without the last pane, since that’s not finished) if there are no objections. ---
**Author:** ![Tim\_M](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/tim_m/32/2_2.png) [@Tim\_M](https://forum.vassalengine.org/u/Tim_M)\ **Post date:** [October 13, 2008, 11:14pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/2 "2008-10-13T23:14:53Z")
Looks good, Now a dumb question 🙂 In the version where you don’t want bug reports : Is it because? A: The bug script checks against reported bugs on server so as not to duplicate another report of the same thing B: Its not an engine bug but something else like module problem Either reason shouldnt the message specify why so users have a direction where to go after / what to do if its a:) to simply see the progress of the already reported bug or b: contact relevant party that needs to know (module maker/forums?) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![mkiefte](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/mkiefte/32/25_2.png) [@mkiefte](https://forum.vassalengine.org/u/mkiefte)\ **Post date:** [October 13, 2008, 11:17pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/3 "2008-10-13T23:17:10Z")
Very cute. I like it. - M. 2008/10/13 uckelman \<[messages@forums.vassalengine.org](mailto:messages@forums.vassalengine.org) ([messages@forums.vassalengine.org](mailto:messages@forums.vassalengine.org))\> > [@](#): > > Here’s a demo for the improved Bug Dialog I’ve been working on: > > [http://www.nomic.net/~uckelman/tmp/vassal/BugDialogTest.zip](http://www.nomic.net/%7Euckelman/tmp/vassal/BugDialogTest.zip) > > There are a shell script and a batch file in the archive from which you can > run the demo. What you’ll see are three paths through the Bug Dialog, one > where we want bug reports from your version of VASSAL, one where we don’t > want bug reports, and one where the bug report check fails. > > Comments welcome. I’d like to include this in beta4 (without the last pane, > since that’s not finished) if there are no objections. Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [October 13, 2008, 11:21pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/4 "2008-10-13T23:21:42Z")
Thus spake “Tim McCaron”: > [@](#): > > Looks good, > > Now a dumb question 🙂 > > In the version where you don’t want bug reports : > > Is it because? > > A: The bug script checks against reported bugs on server so as not to > duplicate another report of the same thing > > B: Its not an engine bug but something else like module problem Neither. The check is against the version number. This is to save us from getting bug reports from versions of VASSAL once they’re no longer current. > [@](#): > > Either reason shouldnt the message specify why so users have a direction > where to go after / what to do if its a:) to simply see the progress of the > already reported bug or b: contact relevant party that needs to know (module > maker/forums?) Should we provide a link for downloading a newer version here? – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![mkiefte](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/mkiefte/32/25_2.png) [@mkiefte](https://forum.vassalengine.org/u/mkiefte)\ **Post date:** [October 13, 2008, 11:32pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/5 "2008-10-13T23:32:04Z")
> [@](#): > > Should we provide a link for downloading a newer version here? Definitely. - M. Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![Tim\_M](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/tim_m/32/2_2.png) [@Tim\_M](https://forum.vassalengine.org/u/Tim_M)\ **Post date:** [October 13, 2008, 11:49pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/6 "2008-10-13T23:49:51Z")
> [@uckelman](#): > > Thus spake “Tim McCaron”: > > > [@](#): > > > > Looks good, > > > > Now a dumb question 🙂 > > > > In the version where you don’t want bug reports : > > > > Is it because? > > > > A: The bug script checks against reported bugs on server so as not to > > duplicate another report of the same thing > > > > B: Its not an engine bug but something else like module problem > > Neither. The check is against the version number. This is to save us > from getting bug reports from versions of VASSAL once they’re no longer > current. > > > [@](#): > > > > Either reason shouldnt the message specify why so users have a direction > > where to go after / what to do if its a:) to simply see the progress of the > > already reported bug or b: contact relevant party that needs to know (module > > maker/forums?) > > Should we provide a link for downloading a newer version here? > > – > J. I think providing a link might be a good idea. But now you got me thinking! You said the script is not checking against reported bugs on the server. Wouldnt you want to (if it is possible) so as to prevent a flood of bug duplication - Im guessing this is a big if? And if you were able to do that, would you then not want to enable reporting of previous versions of the engine so that a bug that may have never been encountered (nor fixed with later engine version) can still be reported? Theoretical utopian idea 🙂 ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [October 14, 2008, 9:29am UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/7 "2008-10-14T09:29:59Z")
Thus spake “Tim M”: > [@](#): > > But now you got me thinking! You said the script is not checking against repo > rted bugs on the server. Wouldnt you want to (if it is possible) so as to pre > vent a flood of bug duplication - Im guessing this is a big if? And if you we > re able to do that, would you then not want to enable reporting of previous v > ersions of the engine so that a bug that may have never been encountered (nor > fixed with later engine version) can still be reported? We had the most duplicates during beta3 that I expect we’ll ever have, due to catching a lot of old, previously-unknown bugs. I handled most of the duplicates, by hand. It wasn’t that bad. If we have fewer than 20 bug reported per day, I can handle it myself using SF’s bug tracker. I could handle more in the same time with Bugzilla. We never reached that level of reports with beta3. Also, there’s sometimes useful information in duplicates. E.g., there were a number of bug reports where the first instance had no contact information or description, but subsequent “duplicates” did. I’m still not convinced that we can do anything reliable w/r/t automating duplicate checking, since it’s possible for two different bugs to generate stack traces which have the same last line, and also possible for the one bug to generate two stack traces which don’t. – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [October 14, 2008, 9:36pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/8 "2008-10-14T21:36:17Z")
Thus spake “Tim M”: > [@](#): > > I think providing a link might be a good idea. Here’s a modified version with a link for downloading a current version of VASSAL. Is this too subtle? [nomic.net/~uckelman/tmp/vass … gTest2.zip](http://www.nomic.net/~uckelman/tmp/vassal/BugDialogTest2.zip) – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![Tim\_M](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/tim_m/32/2_2.png) [@Tim\_M](https://forum.vassalengine.org/u/Tim_M)\ **Post date:** [October 14, 2008, 9:47pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/9 "2008-10-14T21:47:27Z")
That works. Might want to reword slightly “If you can reproduce this bug with A current version…” To “If you can reproduce this bug with THE current version…” The former implies there are multiple current versions available, there shouldn’t be. Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [October 14, 2008, 9:51pm UTC](https://forum.vassalengine.org/t/improved-bug-dialog-demo-for-beta4/1102/10 "2008-10-14T21:51:23Z")
Thus spake “Tim McCaron”: > [@](#): > > That works. > > Might want to reword slightly > > “If you can reproduce this bug with A current version…” > > To > > “If you can reproduce this bug with THE current version…” > > The former implies there are multiple current versions available, there > shouldn’t be. That’s intentional. Much of the time there _are_ multiple current versions available. Right now, 3.0.17 is the current release and 3.1.0-beta3 is the current beta, e.g. – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))