The class files are not the problem. They are all in the MDX file where they need to be. The problem is getting the right statements into the buildFile that goes at the root of the MDX archive. When I use VASSAL extension editor to add my class to my extension, then save it, VASSAL doesn't save the right info in the buildFile that's in the now-saved MDX archive.
I tried a few things with manually editing the buildFile inside my MDX archive using Rodney's example below, but to no avail. Sorry if this sounds terse. I do very much appreciate you trying to help. I'm just frustrated that I can't get this working. If I could overcome this hurdle, I could get to the real work of making a really nice extension, but I'm spending all of my time fighting with VASSAL. Is there someone who can try to mimic my steps and see if they see the same results? Here is what I'm doing: 1) Create a new extension, don't do anything to it, just save it off. 2) Add a .class file to the extension archive. 3) Edit the extension and tell it about the class you've added. 4) Save the extension. 5) See if the buildFile in the saved extension has anything in it about the class you told it about in step 3. Mine doesn't. Thanks, Scott --- In [email protected], "countermancx" <[EMAIL PROTECTED]> wrote: > > hi Scott, I'd try 'manually' adding your classfile to your mdxfile. > An mdx or mod file is a zipfile, Associate those file-extensions w/ > WinZip. Also, turn on Paths in WinZip > Options > Configuration > > View > Columns. Dbl-click your mdx file so it opens in a WinZip app- > window. Drag your classfile from Explorer & drop it in the WinZip > window, an Add dlog will open, both 'save full path' & '8.3 format' > should be unchecked. > hth > > --- In [email protected], "aslbuckwheat" <[EMAIL PROTECTED]> wrote: > > > > Hi Rodney, > > > > I did both steps exactly as you describe. The problem seems to be > > that the buildFile doesn't get written out correctly. > > > > After doing the "Add Imported Class" in the extension editor, it > works > > great - I see my button and can use the flowchart. I then > tried "Save > > As", but the buildFile in the .mdx that gets written out doesn't > have > > the information on my custom class in it. > > > > I will try manually editing the buildFile to see if I can get it to > > work. Is the format of this file documented anywhere? > > > > Thanks > > > > Scott > > > > --- In [email protected], Rodney Kinney > <[EMAIL PROTECTED]> > > wrote: > > > > > > There are two steps. One is to zip the .class file into the .mdx > > file by > > > hand. Second is to edit the extension in VASSAL, right-click on > the > > module > > > folder and select "Add Imported Class" with the name of the class > you > > > wrote. The buildFile you quoted looks like you didn't do the > second > > step. > > > If it's all set up right, you should see entries like > > > > > > <VASSAL.build.module.ExtensionElement > target="VASSAL.build.module.Map:"> > > > > > > in the buildFile. > > > > > > 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/
