Jason Pagura
2008-09-30 21:36:16 UTC
The change log for the latest version (I'm using
FontForge_macX.4_py2.3-20080927) indicates the following:
• Change the menu handler so it can draw mac menu icons (cloverleaf
for command, up arrow for shift, ^ for control and weird squiggly for
option).
• Remove the hack that if the modifier mask for the command key was
set then we'd also set the control mask (this meant that the command
key would work as control, but it meant it could only work as
control).
• Let the command key work as itself, and put in special code to check
whether X11 is going to give us the command key (or will that key be
used in the X11's own menubar). If we get command then we load a
special set of keymap bindings (which, presumably, will use command).
If we don't find a special set of keymaps, then fall back on normal
processing.
So I've installed this new version and my command key no longer works
and ^ rather than the cloverleafs appear in the menus. Is there a
preference I have to tick either in X11 or FontForge in order to get
it working again?
The "Enable Keyboard Shortcuts under X11" pref from X11 seems to not
correct this situation in either position. Rather, it switches between
activating the X11 menu shortcuts and acting as if no modifier key is
held at all. That is, when I strike command-M, the active window
minimizes when this pref is on, and the selected glyph changes to "m"
when it's off, whereas before this would activate the Merge Points
function.
The control key functions as indicated by ^ in the menus, so I can
still work with that, but it is an inconvenience in retraining my
fingers to reach a different modifier key.
FontForge_macX.4_py2.3-20080927) indicates the following:
• Change the menu handler so it can draw mac menu icons (cloverleaf
for command, up arrow for shift, ^ for control and weird squiggly for
option).
• Remove the hack that if the modifier mask for the command key was
set then we'd also set the control mask (this meant that the command
key would work as control, but it meant it could only work as
control).
• Let the command key work as itself, and put in special code to check
whether X11 is going to give us the command key (or will that key be
used in the X11's own menubar). If we get command then we load a
special set of keymap bindings (which, presumably, will use command).
If we don't find a special set of keymaps, then fall back on normal
processing.
So I've installed this new version and my command key no longer works
and ^ rather than the cloverleafs appear in the menus. Is there a
preference I have to tick either in X11 or FontForge in order to get
it working again?
The "Enable Keyboard Shortcuts under X11" pref from X11 seems to not
correct this situation in either position. Rather, it switches between
activating the X11 menu shortcuts and acting as if no modifier key is
held at all. That is, when I strike command-M, the active window
minimizes when this pref is on, and the selected glyph changes to "m"
when it's off, whereas before this would activate the Merge Points
function.
The control key functions as indicated by ^ in the menus, so I can
still work with that, but it is an inconvenience in retraining my
fingers to reach a different modifier key.
--
--
Jason Pagura
zimbach at gmail dot com
--
Jason Pagura
zimbach at gmail dot com