I met with the same problem after upgrading from Ubuntu 16.04 to Ubuntu 16.10
with glibmm-2.4 2.48.1 and gtkmm-3.0 3.20.1.
Have you found a solution?
/Kjell
On 2016/09/19 12:10, D. B. wrote:
I noticed this in Builder, but it applies equally to DevHelp in the
main (which Builder just call
On Mo, 2016-09-26 at 22:26 +0200, Murray Cumming wrote:
[snip]
> I don't think it's likely to work so I'd rather just wait and see
> what
> actually happens. At the least, it just looks like a suggestion that
> they want to start working more now on a parallel-installable GTK+ 4.
> That would be ni
On Tue, 2016-10-25 at 16:22 +0200, Kjell Ahlstedt wrote:
> Gtk+ has announced a new versioning scheme:
> https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-pr
> omise-in-gtk
> Now the gtk+ developers have created a gtk-3-22 branch and started
> removing deprecated API in the master
Hi guys,
I'm looking for the way, in Gtk+, to reprogram the keyboard keys values...
Maybe, should be possible from using: (I don't know)
Glib::RefPtr device_keyboard =
...get_display()->get_default_seat()->get_keyboard();
(I don't know if I explained it so clearly...but I hope so though)
Glus
Hi,
What you're asking doesn't make sense - unless you're planning to drive
your users crazy.
You probably don't want to change the value that key returns; it's more
likely you're trying to connect to a
Gtk::Widget::signal_key_press_event(). That lets you do what you want
with the signal w
