Re: Fwd: Reprogramming keyboard keys

[Kjell Ahlstedt <kjell ahlstedt bredband net>]

There is an alternative:

entry.signal_key_press_event().connect(sigc::mem_fun (*this, &MainWindow::get_key_info), false);

i.e. after==false in the call to Glib::SignalProxy::connect().

Have you seen what's said about keyboard events in the gtkmm tutorial?
https://developer.gnome.org/gtkmm-tutorial/stable/chapter-keyboardevents.html.en
https://developer.gnome.org/gtkmm-tutorial/stable/sec-xeventsignals.html.en

/Kjell

Den 2016-10-30 kl. 10:46, skrev Glus Xof:

Thanks Phil, that's it !

Glus

2016-10-30 1:20 GMT+02:00 Phil Wolff <adiabat centurylink net>:

Try this modification of your example: http://pastebin.com/x6tfK1Nv


On 10/29/2016 02:46 PM, Glus Xof wrote:

Hi Ian,

Thanks again but... I honestly don't see how to solve my problem...

What I really need is to catch the value when a key is pressed... not merely to know when the *entry* value has changed: What can I do from that ?...and How to know which value has changed ?. You see what I mean ?

Please, take this piece of code http://pastebin.com/LqTrph4i, and you'd verify that the handler "get_key_info" is not called when a key is pressed. And the question is... How to force it ?

Thanks,

Glus