> I'm the guilty party and Rodney hit the nail right on the head. The > CH modules do use a VASL custom Java class. > > Rodney will the VASL classes not be compatible from now on? Until I > reload VASSAL and edit the modules what version of VASSAL would one > have to use?
They'll be incompatible from this point forward, but I believe they should work with VASSAL 2.0. You can update the modules by just swapping in the new .class files from the latest VASL module. It was bad form on my part to break backward compatibility with custom classes. I try to avoid it when possible, but sometimes an improvement justifies it. If you make a shortcut that launches the module directly, you can specify the VASSAL version to use, so the shortcut won't break even if VASSAL changes to be incompatible down the line. rk [Non-text portions of this message have been removed] ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/IMSolB/TM --------------------------------------------------------------------~-> 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/
