Yes - that would be a good feature in any module - key usage matrix

Tim

 

  _____  

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Jerry
Sent: Wednesday, January 03, 2007 5:53 AM
To: [email protected]
Subject: Re: [vassalengine] Re: Request for Feature

 

Hi Brent, 

That would be better , however this wasn't to do with CC that's why I
messaged here.. have some other projects ,FoF and stuff for DVG and even
personal stuff , love to finish Carrier think I picked that one up to do two
years ago. 

Thanks .. 

When this lot of development is done I'm going to reset up my Ecclipse kit
First thing I'm going to do is to write a mini data dictionary for Vassal to
document all KEYS used and where sorted by command then watched then
performed.

CC uses just about every combination.



Jerry

-------Original Message-------

From: Brent Easton
Date: 01/03/07 11:40:32
To: vassalengine@ <mailto:vassalengine%40yahoogroups.com> yahoogroups.com
Subject: Re: [vassalengine] Re: Request for Feature

Hmm,

What I am thinking is we get the $PreviousLocationName$ working and have
created units run the same auto-move key. You could tell the difference
because a created unit would have $PreviousLocationName$ = "".

Cheers,
Brent.

*********** REPLY SEPARATOR ***********

On 3/01/2007 at 10:45 AM Jerry wrote:

Happy New Year to all. 

In addittion to the option to specify a key command when ending movement
pieces on a map could you have a seperate one for units created on that map,
we could still specify the same one so it can default to using the end
movement one for backward compatibility. As there is a report on created
hope this will be an easy one to implement. 

Regards 

Jerry 

[Non-text portions of this message have been removed]

__________________________________________________________
Brent Easton 
Analyst/Programmer 
University of Western Sydney 
Email: [EMAIL PROTECTED] <mailto:b.easton%40uws.edu.au> edu.au

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]

 



[Non-text portions of this message have been removed]

Reply via email to