| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Resolves #683474.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
So that we clear its pointer also in case somebody else calls
gtk_container_remove() on the button.
Fixes criticals at startup in e.g. Nautilus.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Be a bit more careful in get_pango_attr_list() and
get_utf8_preedit_string() to ensure that the client_window is properly
created before proceeding, to avoid access violation/segfault crashes on
Windows with IME installed, especially when running the pickers demo.
https://bugzilla.gnome.org/show_bug.cgi?id=682919
|
|
|
|
|
|
|
| |
This way, we can ensure that width/height changes due to the use of
gtk_entry_set_attributes() are correctly reflected in the size request.
https://bugzilla.gnome.org/show_bug.cgi?id=683168
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=683168
|
|
|
|
|
| |
GTK_STYLE_CLASS_INVERTED_CURSOR_HANDLE is no longer defined
as it was left unused by commit 81045779f6
|
|
|
|
|
|
|
| |
Don't hook on the widget style context and set up instead
a widget path for itself. Also use a common style class
for both handles, with an extra top/bottom class for each
handle.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Or rather: Implement it for backgrounds, as the animation rules for
arrays vary by property.
|
|
|
|
|
|
|
| |
This is to allow animating arrays properly. I'm not really thrilled
about this solution (we leak propertys into the values again...), but
it's the best I can come up with - I prefer it to having N different
array types...
|
|
|
|
|
| |
CSS arrays aren't empty, even the ones that appear empty contain one
"none" element.
|
|
|
|
| |
Arrays that support it, handle it themselves.
|
|
|
|
|
|
| |
I want to get away from the ability to have 0-length arrays, all css
arrays are single element.
Even if the element is "none", it is still a "none" element.
|
| |
|
|
|
|
|
|
| |
The GTK_TEST_TOUCHSCREEN envvar is now checked in entries
and textviews to allow testing of text handles with other
kinds of devices.
|
|
|
|
|
|
|
|
|
|
| |
GtkTextHandle is used to indicate both the cursor position
and the selection bound, dragging the handles will modify
the selection and scroll if necessary.
Backwards text selection is also blocked for touch devices,
so the handles don't get inverted positions and possibly
obscure portions of the selected text.
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkTextHandle is used to indicate both the cursor position
and the selection bound, dragging the handles will modify
the selection and scroll if necessary.
Backwards text selection is also blocked for touch devices,
so the handles don't get inverted positions (This is more
important though on GtkTextView, as inverted handles may
obscure portions of the selected text, good for consistence
though)
|
|
|
|
|
|
|
|
|
|
| |
This is a helper object to allow text widgets to implement
text selection on touch devices. It allows for both cursor
placement and text selection, displaying draggable handles
on/around the cursor and selection bound positions.
Currently, this is private to GTK+, and only available to
GtkEntry and GtkTextView.
|
|
|
|
|
|
| |
GtkTextHandle creates temporary override redirect windows, but still
hook to the text widget for events, so those are effectively captured
by GtkScrolledWindow if a text widget is within it
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A change in xkeyboard-config 2.4.1 made it so that function keys
now have a shift level which has the same symbol, but 'eats' the
shift modifier. This would ordinarily make it impossible for us
to discriminate between these key combinations.
This commit tries harder to discriminate in 2 ways:
- XKB has a mechanism to tell us when a modifier should not be
consumed even though it was used in determining the level.
We now respect such 'preserved' modifiers. This does not fix
the Shift-F10 vs F10 problem yet, since xkeyboard-config does
not currently mark Shift as preserved for function keys.
- Don't consume modifiers that do not change the symbol. For
the function keys, the symbol on the shift level is the same
as the base level, so we don't consider Shift consumed.
For more background on the xkeyboard-config change, see
https://bugs.freedesktop.org/show_bug.cgi?id=45008
https://bugzilla.gnome.org/show_bug.cgi?id=661973
|
| |
|
| |
|
|
|
|
| |
Also restore missing copyrights.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 6e6487b461adf2628f49fc257a7a30a2346e5a25.
|
|
|
|
|
|
|
| |
By removing an existing child in add, if it is our own arrow,
we can make things work better in GtkBuilder.
https://bugzilla.gnome.org/show_bug.cgi?id=682291
|
|
|
|
|
|
|
|
| |
This was reported in bug 682291.
https://bugzilla.gnome.org/show_bug.cgi?id=682291
Signed-off-by: David Zeuthen <zeuthen@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Showing mnemonics immediately on modifier press can be annoying and
distracting when the user is just trying to Alt+Tab into another
application/window since the mnemonic will show up and quickly vanish
again when we receive the focus out event.
https://bugzilla.gnome.org/show_bug.cgi?id=672431
|