Changing the functionality of the Layer trait just so it can be consistent as with other traits may not be the best thing to do. Too many modules depend heavily on the usage of the Layer trait that they may be affected and have to be revised if things were to start functioning differently because the keys/field in question are used/changed..if it were a trait improvement/addition then perhaps by all means it should be done, but otherwise it is probably best to leave it as is
_____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 3:18 PM To: [email protected] Subject: RE: [vassalengine] Re: Layer activation & Numpad Rodney, You lost me there :-) The only 'modifier' that can alter what a Numpad key returns is SHIFT and I do take care not to use it otherwise I would end up getting PageUp, PageDown, Insert and all those stuff I don't want. Even without any modifier, it's just that when I press Numpad1 in all other traits or in other fields of Layer, I do get Numpad1 whereas in Layer activate field I get a '1'. Is this by design or is this an error? This is the only trait so far I found that behaves like this. David ROBERT [Non-text portions of this message have been removed] 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/
