After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 133545 - gok frequency based compose keyboard modifier needs hookup
gok frequency based compose keyboard modifier needs hookup
Status: RESOLVED FIXED
Product: gok
Classification: Deprecated
Component: general
unspecified
Other Linux
: High major
: ---
Assigned To: bill.haneman
bill.haneman
Depends on: 135841
Blocks:
 
 
Reported: 2004-02-05 19:28 UTC by David Bolter
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to connect shift modifier to alpha and freq keyboards, and also supply shift keys. (22.18 KB, patch)
2004-03-30 12:56 UTC, bill.haneman
none Details | Review
revised patch as committed to cvs. (22.34 KB, patch)
2004-03-30 13:06 UTC, bill.haneman
none Details | Review

Description David Bolter 2004-02-05 19:28:16 UTC
When trying out the gok_keyboard_get_alpha_by_frequency code path (requires
code modification) the resulting compose keyboard doesn't seem to respond
to the modifier keys.

Trying shift doesn't seem to change the "level" of the label or output...
Comment 1 bill.haneman 2004-02-06 17:15:36 UTC
bumping severity up so it appears on my radar ;)
Comment 2 bill.haneman 2004-03-30 12:56:20 UTC
Created attachment 26093 [details] [review]
patch to connect shift modifier to alpha and freq keyboards, and also supply shift keys.
Comment 3 bill.haneman 2004-03-30 13:06:21 UTC
Created attachment 26095 [details] [review]
revised patch as committed to cvs.

I am committing based on initial review by David - however I'd appreciate it if
you'd glance at the final patch (David) as it differs a bit (mostly in the
addition of shift/modifier keys to the alpha keyboards themselves).  I also
added a BackSpace key to these keyboards, on the assumption that a destructive
backspace would generally be desirable in this context.

There's also a minor correction to the code which creates 'frequency' keyboards
- I've given them the correct name ('alpha-frequency'), and pass a
KeyboardLayouts argument to the compose keyboard create function, so that the
frequency-based keyboard uses UPPERL by default.  Note however that the
resulting feature isn't working as expected - the keyboard's layout flag seems
to be ignored when the keyboard is actually laid out.  Perhaps you could
revisit the old layout bug?  Thanks