I've had two complaints that Solo ought to recognise the numeric
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Thu, 12 May 2005 18:25:57 +0000 (18:25 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Thu, 12 May 2005 18:25:57 +0000 (18:25 +0000)
commit3c833d458bd4db0fe5ab9b5234e17eac28e0cab4
treeaae64cd5bea2dd7c44230cb0ed9d68a76c937395
parent818752113d2ba0ab8661365c5e81665e8fc6d15f
I've had two complaints that Solo ought to recognise the numeric
keypad. The reason it doesn't is because front ends were carefully
translating the numeric keypad into 8-way directional keys for the
benefit of Cube. Therefore, a policy change:
 - front ends process the numeric keypad by sending MOD_NUM_KEYPAD |
   '3' and similar
 - front ends running on a platform with Num Lock SHOULD do this
   _irrespective_ of the state of Num Lock
 - back ends do whatever they see fit with numeric keypad keys.
Result: the numeric keypad now works in Solo, and also works in OS X
Cube (which it previously didn't because I forgot to implement that
bit of the front end!).

git-svn-id: svn://svn.tartarus.org/sgt/puzzles@5774 cda61777-01e9-0310-a592-d414129be87e
cube.c
gtk.c
osx.m
puzzles.h
solo.c
windows.c