Thus spake Gary Krockover: > Joel, > > Are those dialog boxes controllable on a case by case basis? In otherwords, > when you go to launch a new module, you get the Java version of the file open > window, but when you go to select a saved game, you get the OS native versio > n.
Oh, right. You're picking up on an inconsistency between the part of VASSAL that's open-source in 2.x and the part that's not. The launcher (closed) uses Swing dialogs, while what we're using in the rest (open) of VASSAL has been in flux since 2.9.something, where "something" corresponds to the first version released after I started writing code. That inconsistency will be resolved in 3.x, since the launcher part will be also be open (and is already, in our source repository), though I don't know in which direction the inconsistency will be resolved. > The one advantage of the Java based window is that it not only remembers the > last folder that was browsed but the position in that folder. So, if you're > adding a bunch of new pieces and have the images in an alpha-numeric list, yo > u then just pick the next image from the file chooser when you open that wind > ow. I tend to name my pieces something like: > > Ger-Inf-32div.gif > > So, after adding the German 32nd Division, it's easy to then pick > > Ger-Inf-33div.gif next. > > I agree with Michel that the OS Native window is better for the saved game/lo > g file selection. My "solution" to all of this was to make a file chooser wrapper that gave you a native one on Windows and Mac OS X, and a swing one otherwise. What you're noticing here might be a bug in my wrapper. I'll look into that. -- J.
