Being in the IT business I can only agree with you that it behaves differently from kb to kb, system to system. But here the problem is with the same kb, same system, same Vassal version, same module. It's just that the behavior is different from one part of a trait and another. Not even different traits. Just between the field where on put the command to activate a layer and the field to put the command to reset/randomize a layer.
I only want the Layer trait to be consistent with what other trait are doing: treating a Numpad key as a numpad key. Can we hope for this in next patch/version of the code? --- In [email protected], "Rodney Kinney" <[EMAIL PROTECTED]> wrote: > > > I tested this layer and VASSAL activate/deactivate it when I press the "1" > > key or the Numpad-1 without making any difference betweent the two keys > > > Unfortunately, I don't think the Numpad behaves consistently across > different keyboards. For example, the NumLock key changes what you get when > you press one of the numkeys. There might be a way to straighten it all > out, but I'm not surprised that it's confusing/inconsistent. > > rk > > > [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/
