J,
What about expanding the cut and paste ability within the editor itself so we can at least cut and paste traits from within the pieces and protos themselves? Not module to module at this time or is this still because of the same limitation? Cut and Paste as it is now is not to useful and painfully slow by only letting you select one piece at a time. Moving a lot of pieces from a palette to At start stacks can take quite a while.. Tim _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Joel Uckelman Sent: Thursday, March 29, 2007 3:41 PM To: [email protected] Subject: Re: [vassalengine] Re: Transfer Between Modules Thus spake "alexiusexfalso": > Well, looking on the bright side, mine is now the best known Vassal > query in history... > > Unzipping...shall try that, thanks for the tip. > > The photo idea thing sounds worth the try too; I'll give it a shot. I'd recommend against screen capturing the images, since you can just get them from the images directory in the module---far, far simpler. > It seems the Vassal software doesn't allow this kind of passage of > data directly, which is odd as it would surely be very useful. Or > does it have the capacity to do that hidden somewhere? The key for transferring data between modules is having a buildfile format which is entirely human-readable, so that you could do such a transfer via cut-and-paste in your favorite text editor. This won't be in 3.0, but probably in some 3.x for x > 0. I expect to work on it at some point this summer. -- J. [Non-text portions of this message have been removed]
