Gary, You might want to grab the VASSAL 2.5b beta to test the autoimage function. With the next release, it's going to be built in, and function differently. On the whole, it works *extremely* well! The module I'm wrapping up right now is using the new AutoImage functionality (just have to wait for the official release). There are a couple bugs in the beta version, but nothing critical--you can find details in the posts I've made here over the last few weeks.
But essentially, there is a slight problem in the positioning of a centered graphic on the last counter in the counter menu--causes it to use the position as the top-left rather than the center (This is already fixed in the upcoming final version). The other bug requires you to select the text type when you make a text entry on the counter, even if you want to keep the default text type. In other words, even though it says "default" under text type, you still have to specifically select "default." This is a fantastic addition to VASSAL, I think you're really going to like it--it's going to make creating modules for even monster games feasible (note I said feasible, not "easy!"). --guy --- In [email protected], Gary Krockover <[EMAIL PROTECTED]> wrote: > > As a follow-up: I'm getting the same error message ("Unable to create class AutoImage.CommandEncoder....") when I open the sample AutoImages.mod that came with the AutoImages package. Sorry if I missed that this is a known issue, or if it is not, could I have a corrupt VASSAL install? > > Gary > > At 10:21 AM 1/19/2006, you wrote: > >Brent/group: > > > >I'm trying to implement AutoImages for the first time in a module. I'm wanting to add the ability to add and modify text on a single counter in the module, with the rest of the counters being already defined and created using traditional images. > > > >Following the instructions and then loading the module to edit, I get the error: "Unable to create class AutoImage.CommandEncoder in *full path to module* AutoImage/AllEmbellishment" > > > >Ignoring that error, I import the class and then go to my prototypes where the specific marker is defined. I noticed that all of my previous traits for the other markers are gone - as if AutoImage is overriding those. > > > >So...first, what is causing that error (yes, I copied the specified folder into the module and rezipped first) and secondly, can I add AutoImages characteristics to a single counter or would I have to use it for all of them? Or, is the error related to why all the previously defined traits are no longer showing up? > > > >Thanks! > >Gary > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/vassalengine/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
