[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Help! Keyboard problems

From: Richard Shann
Subject: Re: [Denemo-devel] Help! Keyboard problems
Date: Sat, 08 Dec 2018 17:16:29 +0000

On Fri, 2018-12-07 at 20:37 +0000, Richard Shann wrote:
> On Fri, 2018-12-07 at 17:59 +0000, Richard Shann wrote:
> > On Fri, 2018-12-07 at 16:34 +0100, address@hidden wrote:
> > > [...]
> > > for example if you run the command Score->Comment you get an
> > > editor
> > > [...]
> > 
> > I have tested the AppImage under a live Distro of Ubuntu 18.04, but
> > it
> > probably had a US keyboard setup - I'll re-test to see if I can
> > reproduce your problem.
> This was successful, I see the same problem running the AppImage
> under
> a live Ubuntu 18.04 distro - the difference is only quite subtle as
> it
> only affects a few keys like the # and ? but it is quite easy once
> you
> know what to look for.
> I'll be able to track down what is going on now I think... thank you
> for your feedback.

I think I have an understanding of the problem. It affects users who
have more than one keymap installed on their system. The keymap that
Denemo is launched in is used for widgets like text editors that Denemo
launches, but keystrokes directed to the Denemo Display (aka Edit
window) are not treated as text, instead a call is made to ask for a
translation of the key code according to something called the keymap of
the default display. (This is a call to gdk_keymap_get_default() in the
source code).

It would seem (if you are right about the behavior having changed) that
previously this Gdk call got the keymap Denemo had been launched with,
but now it gets the desktop-wide default. Reading the documentation, I
see that the call to gdk_keymap_get_default() has been deprecated since
version 3.22 of Gtk, so I have upgraded the source code to use this
newer version, but I suspect this will not change anything. However,
I've uploaded an upgraded version of Denemo at

I don't expect this will behave differently, but it will print out what
it is doing with the keypress.

There is a setting under

Edit->Change Preferences->Command Behavior->Strict Shortcuts

which avoids the call to re-encode the keypress, however the standard
shortcuts for inserting a note before the cursor (such as A, A) and
other shortcuts involving the Shift key may not work - you have to use
the CapsLock in that case, I think. Also, you have to have the NumLock
set correctly for using the numeric keypad to enter notes (again, I

Of course, you can re-define all the shortcuts to suit the keymap being
used. If you do create a set of shortcuts useful for others please post
them here.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]