Hi Gary, With AutoImage being merged into core vassal, I haven't been keeping an eye on AutoImage itself. If you are starting a new module, try out the 2.5 beta version as Guy suggested. It is virtualy identical. Major differences from AutoImage (AI) to GamePieceImage (GPI) are: - AI Images appear directly in the Image drop-down box, in BasicPiece or Layer. No need for AutoImage trait or AI_Embellishment class. - With GPI, you need to create a seperate definition for every counter image. It does not have the Variable Text option. - GPI is getting a new item type - TextBox - which will be perfect for setting up card text. It sets up a variable size label that allows you enter HTML to get word wrapping, colors, styles, sizes etc. The buildfile structure for AI and GPI are identical and compatible, it is possible to convert from AI to GPI by careful editing of the buildfile and changing the name of the AI classes to the GPI classes. Cheers, Brent.
--- 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/
