The other thing was I had to import CCEmbellishment to get the CC Layer trait but all is working now.
Next question, I did all of this in my main module, where it is working. Is it possible to leave the main module alone and do this in a module extension? IE I'm creating a module extension just for new counters that use CC Layer. Or does the CCCommandEncoder have to be declared in the main module? John --- In [email protected], "John" <[EMAIL PROTECTED]> wrote: > > Ah, I was replacing the vassal command encoder with the cc command > encoder instead of just adding it above it in the build file. > > Thanks to all for the help, > > John > > --- In [email protected], "Tim McCaron" > <timothy.mccarron@> wrote: > > > > John, > > > > > > > > There is a folder inside the mod called "cc". You will need to put > this > > entire folder into your module. > > > > You will also have to edit the buildfile after to add the command > encoder > > before the vassal encoder as Brent mentioned before for it to > work. Then > > import the trait > > > > > > > > Tim > > > > > > > > _____ > > > > From: [email protected] > [mailto:[EMAIL PROTECTED] On > > Behalf Of John > > Sent: Sunday, February 04, 2007 11:13 AM > > To: [email protected] > > Subject: [vassalengine] Re: Trying to use class from another module > > > > > > > > Thanks for the reply Brent. > > > > The CCLayer trait will be nice to have in 3.0. I could not find > the > > CCLayer class in any of the folders of the Combat Commander > module. > > Is it named something other than CCLayer.class? > > > > John Boone > > > > --- In vassalengine@ <mailto:vassalengine%40yahoogroups.com> > > yahoogroups.com, "Brent Easton" <b.easton@> > > wrote: > > > > > > Hi John, > > > > > > CCInfo has nothing to do with CCLayer, it just accesses my > custom > > terrain modification and returns the name of terrain in the > current > > hex as $CurrentTerrain$. > > > > > > CCLayer is stand-alone and does not need CCInfo. The changes in > > CCLayer will probably be incorporated into vassal 3.0 at some > stage. > > > > > > CCInfo and CCLayer are both counter traits, they cannot be > > imported anywhere in the module tree, they must be imported into a > > counter. When you are editing an individual gamepiece (or > prototype) > > and have the window with the list of traits up, then click the > > Import button on the bottom left of the window and enter > cc.CCLayer. > > > > > > You will also need to install the custom command encoder > > cc.CCCommandEncoder - there is information on how to do this at > the > > bottom of the Programming tutorial on the VASSAL doco site > > (http://www.vassalen > > <http://www.vassalengine.org/wiki/doku.php?id=programming> > > gine.org/wiki/doku.php?id=programming). > > > > > > Regards, > > > Brent. > > > > > > >*********** REPLY SEPARATOR *********** > > > > > > > >On 4/02/2007 at 4:48 AM John wrote: > > > >Thanks for your quick reply but I'm not sure I follow you. > > > > > > > >Does it matter where in the editing menu you try to import a > > class? > > > >I tried it at the top level, on Game Piece Prototype > Definitions, > > Game > > > >Piece Palette, and on an individual piece I defined. I still > get > > the > > > >same error. > > > > > > > >John > > > > > > > >--- In vassalengine@ <mailto:vassalengine%40yahoogroups.com> > > yahoogroups.com, Torsten Spindler <spindler@> > > > >wrote: > > > >> > > > >> On Sun, 2007-02-04 at 04:21 +0000, John wrote: > > > >> > How do I use the CCInfo.class from Combat Commander in > > another > > > >module? > > > >> > > > > >> > I want to use the CC Layer trait. > > > >> > > > > >> > I placed the class files in the module zip and tried to > > import the > > > >> > class but it said that "Class must implement the > configurable > > > >> > interface". > > > >> > > > >> When CCInfo is a trait, it has to be imported by a gamepiece. > > > >> > > > >> Bye, > > > >> Torsten > > > >> > > > > > > > > > > > > > > > __________________________________________________________ > > > Brent Easton > > > Analyst/Programmer > > > University of Western Sydney > > > Email: b.easton@ > > > > > > > > > > > > > > > [Non-text portions of this message have been removed] > > >
