| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
One hunk got lost when cherry-picking the icon view keynav changes.
|
|
|
|
| |
They are added by the binutils gold linker.
|
|
|
|
|
|
| |
Reported by Andika Triwidada in
https://bugzilla.gnome.org/show_bug.cgi?id=618093
(cherry picked from commit 7b2024c1bd4a9b013cec4e4885211c04522a96ab)
|
|
|
|
|
|
|
|
| |
Use ::keynav-failed for arrow navigation in icon views, so that
it is possible to override error handling. Also add API to get the
row/col of an item. With this, it is possible to make arrow keynav
span adjacent icon views, which is desired in the new control-center
shell. testiconview-keynav demonstrates this.
|
|
|
|
|
|
|
|
| |
Changed the way to find the drop widget from a top->bottom recursion
using GdkWindow positions to a liner bottom->top walk up the widget
hierarchy using _gtk_widget_find_at_coords() and
gtk_widget_translate_coordinates(), which both do the right things for
offscreen widgets.
|
| |
|
| |
|
|
|
|
|
|
| |
* gtk_tree_model_get_column_type: transfer none added to the return value
* gtk_tree_model_get_path: value parameter switched from inout to out
so that it is annotated with caller-allocates
|
| |
|
|
|
|
|
|
|
| |
Turn find_widget_under_pointer() into internal API
_gtk_widget_find_at_coords() which is needed for fixing above
bug. This should actually be a public utility function, and will be
moved to another file when its final API has been decided.
|
|
|
|
|
|
| |
To check whether the window has an explicit group
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=618271
|
|
|
|
| |
This reverts commit 821dd33918d80a28a7e47a2aaa2aaaf100b51c1b.
|
|
|
|
| |
* it returns the selection from its priv structure without reffing
|
|
|
|
|
|
|
|
|
|
| |
Includes fixing all callers to use the cairo region API instead. This is
usually just replacing the function names, the only difference is
gdk_region_get_rectangles() being replaced by
cairo_region_num_rectangles() and cairo_region_get_rectangle() which
required a bit more work.
https://bugzilla.gnome.org/show_bug.cgi?id=613284
|
|
|
|
|
|
|
|
|
| |
This completes the move to get rid of using a GdkRegion for the
navigation region and the only user of gdk_region_polygon(). We keep
track of the triangle and compute in/out points ourselves now.
Unfortunately the DRAW_STAYUP_TRIANGLES debugging code doesn't work
using cairo, so I removed it completely.
|
|
|
|
|
| |
Gets rid of some code in preparation to switching to do the computation
completely without GdkRegion.
|
|
|
|
|
|
|
|
| |
This was discussed in bug 613132.
Conflicts:
gtk/gtkbox.h
|
|
|
|
| |
Sync paper size fallbacks with the latest 1.8.1 CLDR table (#618000).
|
|
|
|
|
|
|
| |
* gtk/gtkrange.c: (gtk_range_adjustment_value_change):
Queue the draw also if the range is a scale and the value is drawn,
fixing bug #533946 (Markus Brinkmann), when two HScales use one
adjustment.
|
|
|
|
|
|
| |
Set enter and leave notify mask on header window.
Extract from a patch by Hans van Hintum.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also, added api to allow an input method to internally handle
key press and release events in the GtkTextView and GtkEntry
cases.
This is simply a wrapper to the gtk_im_context_filter_keypress()
function, but It's added to not access the ->im_context
directly.
Based on a Christian Dywan patch
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=163251
|
|
|
|
|
|
|
|
|
|
|
| |
The file removal code was not properly clearing the file=>array index
cache, so later lookups into that cache would return invalid array
indexes.
The easiest way to reproduce it is to create a directory with two files
and deleting both of them.
Reported-by: Javier Jardón <jjardon@gnome.org>
|
| |
|
| |
|
|
|
|
|
| |
This completes the patch of
commit b8ec73a52fe3dc3012db78f45bfcafa2cb3e14ae
|
|
|
|
|
|
|
| |
The macro GTK_WIDGET_SET_FLAGS(w, GTK_VISIBLE) should
still be fixed internally.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=69872
|
|
|
|
|
|
|
|
|
| |
GtkTextView is missing accessors for its sealed hadjustment
and vadjustment members.
This patch adds gtk_text_view_get_hadjustment() and
gtk_text_view_get_vadjustment() to GtkTextView
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=616053
|
|
|
|
|
|
| |
Introduce internal _gtk_widget_set_has_default() for this
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=614515
|
|
|
|
|
|
| |
Introduce internal _gtk_widget_set_is_toplvel() for this
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=614510
|
|
|
|
|
|
| |
Introduce internal _gtk_widget_set_has_grab() for this
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=614513
|
|
|
|
|
| |
Reported by Hernando Torque here:
https://bugzilla.gnome.org/show_bug.cgi?id=616851
|
|
|
|
|
|
| |
Remove the second (and last) internal user of the GTK_HAS_FOCUS flag.
https://bugzilla.gnome.org/show_bug.cgi?id=593671
|
|
|
|
|
|
| |
Remove the original user of the GTK_HAS_FOCUS flags.
https://bugzilla.gnome.org/show_bug.cgi?id=593671
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the only users of the GTK_HAS_FOCUS flag are setting it
before sending a focus change event. This is normally needed by
GtkWindow, but there are widgets that require controlling the focus
of widgets that are semantically their children even though they are
parented to another top-level. Case in point: the quick search entry
for GtkTreeView.
Over the years people have been hacking the focus change out of
gtkwindow.c and gtktreeview.c, thus leaking the direct access of the
GTK_HAS_FOCUS flag.
The simplest way to avoid that is to add a function that sends the
focus change event and controls the setting of the flag, thus removing
the need for external widgets to do the same.
https://bugzilla.gnome.org/show_bug.cgi?id=593671
|
|
|
|
|
|
|
| |
Also, add a note about GTK_BUTTONS_OK, GTK_BUTTONS_YES_NO
and GTK_BUTTONS_OK_CANCEL are discouraged by the GNOME HIG.
https://bugzilla.gnome.org/show_bug.cgi?id=597865
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611957
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611833
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
| |
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611741
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=612351
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611958
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611956
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611952
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611656
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611827
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611829x
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=611634
Signed-off-by: Javier Jardón <jjardon@gnome.org>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=611707
|