You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a custom keyboard layout installed on Windows 7, but fontforge, at least in the initial file picker, seems to be ignoring that somehow, perhaps doing its own interpretation of key up/down sequences rather than obtaining the keycodes from the proper Windows APIs. This makes it rather hard to type file names, especially those using characters not on (or that I can not find on) whatever keyboard model it is using.
The text was updated successfully, but these errors were encountered:
Generally speaking, FontForge was originally written on top of the X Window toolkit (UNIX) so as you point out, it's not a native Windows app. It uses the xkb utility for keyboard handling for instance, and hwile it's configurable via launch flags there's (seemingly) no detection feature.
I have a custom keyboard layout installed on Windows 7, but fontforge, at least in the initial file picker, seems to be ignoring that somehow, perhaps doing its own interpretation of key up/down sequences rather than obtaining the keycodes from the proper Windows APIs. This makes it rather hard to type file names, especially those using characters not on (or that I can not find on) whatever keyboard model it is using.
The text was updated successfully, but these errors were encountered: