| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When drawing the keyboard without having set the groups and levels there
is a segmentation fault:
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe49ae8c9 in draw_key_label (is_pressed=<optimized out>, xkb_height=<optimized out>, xkb_width=<optimized out>, xkb_origin_y=<optimized out>,
xkb_origin_x=<optimized out>, angle=0, keycode=<optimized out>, drawing=0xa540e0, context=0xca6080) at gkbd-keyboard-drawing.c:1017
1017 if (drawing->groupLevels[glp] == NULL)
Fix that.
The widget now is able to draw a keyboard without the keys labels, which
can be useful when testing just the keyboard geometry.
https://bugzilla.gnome.org/show_bug.cgi?id=760988
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When track_modifiers is true and a modifier key gets pressed, do not
free and reallocate the data and, in particular, do not reallocate
drawing->keys zeroing it; this would result in the modifier keys pressed
states to be forgotten and the modifier keys not to be shown as pressed
when in fact they are (the keyboard symbols reflect the shift level
correctly).
Fix the current situation, allowing the modifier keys pressed state to
be drawn correctly.
https://bugzilla.gnome.org/show_bug.cgi?id=734621
|
|
|
|
|
|
|
|
|
|
|
| |
Some keys like the function key "FN" are described in geometry files but
they have no keycode associated to them. You can find such keys in the
thinkpad and in the hhk geometry files.
Allow drawing the shape of these keys with invalid keycodes, and just
skip looking for the labels as the label is derived from the keycode.
https://bugzilla.gnome.org/show_bug.cgi?id=734618
|
|
|
|
|
|
|
| |
* Cleans up a bunch of warnings, and gets g-ir-scanner to actually
recognize the annotations.
https://bugzilla.gnome.org/show_bug.cgi?id=675729
|
|
|
|
|
| |
Implemented in g-s-d through custom scripts
https://bugzilla.gnome.org/show_bug.cgi?id=674874
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=674873
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Spurious double quotes around uidir and iconsdir makes
install attempt to install in '<DESTDIR>"<iconsdir>"'
ie
'/opt/gnome/_jhbuild/root-libgnomekbd\"/opt/gnome/share/libgnomekb/icons\"'
Then install fails to install the data files into the correct directory:
'/opt/gnome/_jhbuild/root-libgnomekbd/opt/gnome/share/libgnomekb/icons'.
It looks like the for loop to install items expands the icons and ui
dirs while the mkdir -p does not.
Fix this issue by removing the double quotes in th Makefile.am around
the iconsdir and uidir assignments.
|
|
|
|
|
|
|
|
| |
Since gkbd_keyboard_config_split_items uses static storage, if
we want to call it twice and compare the results we have to
make a copy.
https://bugzilla.gnome.org/show_bug.cgi?id=673539
|
|
|
|
| |
A part of https://bugzilla.gnome.org/show_bug.cgi?id=660000 fix. The xmodmap config patching should happen regardless of the configuration changes (even if from xkb POV there was no change).
|
|
|
|
|
|
|
|
|
|
| |
commit c9d3c0e939c21230d6088aaf915d9b7d965d97d8 introduced a couple
of calls to gkbd_keyboard_config_split_items with the incorrect
assumption that those calls return newly allocated memory.
This commit drops the wrong free calls.
https://bugzilla.gnome.org/show_bug.cgi?id=670164
|
|
|
|
| |
This reverts commit a6ca20e027edf43df578c7cf1aa26eecb6512540.
|
|
|
|
|
|
|
|
|
|
| |
options should be able to appear in different orders,
or have different group names and still appear as equal.
This commit makes gkbd_keyboard_config_equals more
forgiving.
https://bugzilla.gnome.org/show_bug.cgi?id=670164
|
|
|
|
|
|
|
|
|
|
| |
gkbd_keyboard_config_split_items allocates its out args, but
those allocations aren't getting cleaned up in
gkbd_keyboard_config_copy_to_xkl_config
This commit plugs that leak.
https://bugzilla.gnome.org/show_bug.cgi?id=670164
|
|
|
|
| |
In the GNOME 3 world, there are gnome-shell extensions, there is introspection - so plugins are not necessary any more
|
| |
|
| |
|
| |
|
|
|
|
|
| |
New libxklavier 5.2 provides introspection, so it is now used by libgnomekdb.
Of course, non-introspectable X11 API still provides some warning messages
|
|
|
|
|
|
|
|
| |
... and not a GdkColor. So use the right variable, and the right free function.
Fixes a crash on session startup in gnome-settings-daemon, when using the gnome3
fallback session.
https://bugzilla.gnome.org/show_bug.cgi?id=663816
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=653155
|
|
|
|
|
|
| |
LIBBS don't belong to LDFLAGS anyway and the la files should have all needed
information. The extra LIBS caused jhbuild failure where it would pick up system
libs instead of the ones we just built. Fixes #653155
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=647646
|
|
|
|
|
| |
Using large screens can cause bad, huge, windows
http://bugzilla.gnome.org/show_bug.cgi?id=647646
|
|
|
|
| |
Otherwise build process fails
|
|
|
|
|
|
|
|
| |
There are bugs in both the notification area and in GtkStatusIcon
when it comes to size allocation. This patch tries to work around
them in a way that makes the keyboard indicator come up with a
reasonable size initially, and not resize when clicked.
https://bugzilla.gnome.org/show_bug.cgi?id=642703
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is really a big hack: instead of getting the information about how
to draw the font from a GTK+ style, we get it from the GtkStyleContext
from the tray icon widget embedded in the GtkStatusIcon.
To make this happen, we have to fake the GtkStatusIconPrivate structure,
and we rely on the fact that the tray icon widget is the first element
in this structure.
https://bugzilla.gnome.org/show_bug.cgi?id=642703
|
|
|
|
|
|
|
|
| |
In order to have the shell show it, it needs to "in theory" be
in a menu, even if it's NoDisplay=true. "GNOME;Gtk;Core;" isn't
shown anywhere, so stick it in "System Tools".
https://bugzilla.gnome.org/show_bug.cgi?id=645283
|
|
|
|
|
| |
It was 10, it is 12 now
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=643754
|
|
|
|
|
| |
The formatting of the visible strings changes: no need to prepend the layout
description to the variant description.
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=643190
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
| |
|
|
|
|
|
| |
The code is there, the button can be added back to .ui file if necessary
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
http://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=642903
|
|
|
|
| |
http://bugzilla.gnome.org/show_bug.cgi?id=642903
|
| |
|