Thus spake “bsmith”:
That could make a difference. I didn’t know there was a pref for that,
actually.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Ben Wynniatt-Huse found a drawing bug I introduced which prevented
movement trails from drawing. It’s fixed in 2868:
Thus spake “bsmith”:
I think I get what you want here. I agree that not anchoring the map to
the upper-left would be better. It’s not clear to me how to do that yet,
though.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
What’s left to do before 3.1.0-beta1?
Is there anything else that we must have/do before releasing a beta? I don’t
want to sit on it too much longer—I was hoping we’d put out this release at
the start of December!
Hey it wouldn’t be a real IT project if it wasnt delayed at least 4 weeks 
For the memory-mapped option I’ll do another performance test on an average size module and see what happens. I actually think there are a lot more PBEM games going on than live play so I’m leaning towards turning it off for at least the first full release until we’re comfortable that it is not going to be too big a shock for users.
Personally if I had to choose between 3.0.17 with a 5 second load and 3.1 Beta with a 16 second load time, I would have to go with 3.0.17 purely because I do tons of logs each day; If it affects me then I’m sure it will affect others too.
Here’s the start of a list of things in 3.1.0-beta1:
Bug 1716071: Drag ghosts for multiple selections
Bug 1866161: Exception when deleting initial elements from tabs
Bug 1860941: Do not prompt to start new logfile when already recording
Bug 1716080: Piece traits editor allows removal of BasicPiece trait
Bug xxxxxxx: Zooming now correctly maintains view center.
RFE 1633152: Simplify adjusting Maximum Memory requirements
RFE 1566177: Implement JAI tiled images to reduce memory usage
RFE 1565958: Zooming to larger than 100%
Upgraded SVG library from Batik 1.6 to Batik 1.7
Launch from VASSAL.exe on Windows.
something from r2785 (what?)
Shouldn’t bug fixes go in 3.0 and new features go in 3.1?
On 22/01/2008, uckelman messages@forums.vassalengine.org wrote:
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “Michael Kiefte”:
The last bug fix listed can’t, because it depends on some code which is
in one of the RFEs, which in turn depends on some code in both of the
other RFEs.
My thinking in this particular case is that 3.0 was not an especially
good release, and that putting bug fixes into 3.1.0 will put 3.0 to
rest quicker.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thanks Joel.
Can we put this in a text file which goes out with each release? It would go into the root of the Vassal folder alongside Vassal.bat and Vassal.sh. A history of changes between releases, we could call it “release notes.txt” or something similar.
OK. I tried a similar speed test with the AVL module. All operations take under 1 second except for opening the module.
With memory mapped files turned on, we’re looking at a 5 second load time for the standard scenario. With memory mapped files turned off it takes around 1 second to load. Either way, zoom speed has been dramatically improved regardless of setting!
I would lean towards having memory mapped files turned off by default at this stage. If users are having memory problems then they can always turn it back on.
Thus spake “bsmith”:
Ok. My main reason for developing them was to make it possible to run
large modules with less RAM, which purpose they serve just fine. We
need to be sure to convey to people that it is possible to turn it on,
though.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “bsmith”:
I think we could. I would be inclined to call it RELEASE-NOTES, though,
as is common practice among FOSS projects—either that or make it
HTML, becuase most Windows users aren’t going to know what it is
otherwise.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “bsmith”:
Done, as of uckelman-caching@2877.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
With the new zoom feature, I can’t seem to disable the button.
For example, if I want to have a map zoomed out permanently, without the user having the possibility to change it, I could remove the button text, remove the button icons, and the button wouldn’t show up. But with the new control, the button always shows up (the icon gets reset if i unset it).
Thus spake “tbyrne”:
It had not occured to me that anyone would want that. I’ll look into it,
but not anymore tonight.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
One suggestion for the .bat and .sh files you have. Can you add %* and $* at the ends of the execution lines respectively. I think this will add any parameters from the command line so you can do this:
VASSAL.sh module.mod
or
VASSAL.sh -edit module.mod
And likewise with the .bat file
Thus spake “tbyrne”:
Good catch.
I think “$@” is what we want for the shell script, not $* (unless there’s
some reason to prefer $* of which I’m unaware). “$@” prevents filenames
containg spaces (ewwww!) from being broken into multiple arguments.
I don’t know anything about batch files, really. Is %* the right thing?
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
On 1/23/08, Joel Uckelman wrote:
That makes sense.
I really don’t know, but %* worked on XP when I tried it. I have no
idea if it works on other flavors of windows. I do think that %1 %2
%3 %4 etc. would probably work too, although that’s quite ugly.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “tbyrne”:
I set out to fix this, but instead came across several nasty bugs in Zoomer
which I’ve now fixed. There’s still one left which I don’t know how to fix:
If the initial zoom level is the last zoom level on the list and you remove
that zoom level, then the initial zoom level has to change also. E.g., if
initial was 4 and now the list has only three elements, the initial zoom
level can’t remain 4. Handling this case is no problem. What is a problem
is updating the initial zoom text box in the dialog, since I seem not to
have access to that from within Zoomer. Is there a simple way to get that
text box so I can update it?
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “tbyrne”:
This works for me, as of 2888, but I didn’t do anything which I can see
that would have made any difference:
nomic.net/~uckelman/tmp/vass … vn2888.zip
The way I’m removing the zoom buttons is by clearing the button text
and icon. I don’t see that it’s being reset if I clear them in the
editor and then start a game.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)