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
_____ De : [email protected] [mailto:[EMAIL PROTECTED] De la part de Rodney Kinney Envoyé : mardi 1 août 2006 22:03 À : [email protected] Objet : Re: [vassalengine] Re: Layer activation & Numpad > I only want the Layer trait to be consistent with what other trait > are doing: treating a Numpad key as a numpad key. The reason that Layers act differently is that Layers have the unique ability to define multiple keystrokes for an action. (See the Advanced Layers section in the reference manual.) These are handy features but they have the unintended effect of treating numpad keys differently because you specify a single modifier and multiple keys, while numpad keys behave differently depending on what modifier keys are pressed. rk [Non-text portions of this message have been removed] [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/
