| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=700419
|
| |
|
|
|
|
|
|
|
|
| |
currently it's using the same sizes for natural and minimum, but it
happens that, when it's allowed to use the arrow, the minimum size
can be smaller than natural.
https://bugzilla.gnome.org/show_bug.cgi?id=693227
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711255
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711611
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711611
|
| |
|
|
|
|
|
|
|
|
| |
* gtk/gtkprintunixdialog.c (printer_status_cb): Do not reset the
waiting_for_printer on status change as the default printer might
get added later.
https://bugzilla.gnome.org/show_bug.cgi?id=577642
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=709629
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=709629
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=709629
|
|
|
|
|
|
|
| |
... which are both to be used for links instead of the current
-GtkWidget-link-color and -GtkWidget-visited-link-color
https://bugzilla.gnome.org/show_bug.cgi?id=709629
|
| |
|
|
|
|
|
| |
Too many applications and libraries depend on accessing the internally
created cell renderer. Allow that again, but print a warning.
|
|
|
|
|
|
|
|
|
|
| |
This avoids having Gtk-3.0.gir differ on 32 vs 64 bit, which causes
issues for "multilib" in Fedora/OpenSUSE type systems.
See https://bugzilla.gnome.org/show_bug.cgi?id=711153 for more
information.
https://bugzilla.gnome.org/show_bug.cgi?id=711158
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711324
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711324
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711324
|
|
|
|
|
|
| |
Call gtk_cell_layout_clear() on the area instead of the completion in
gtk_entry_completion_clear_text_column_renderer(), because it is also
called from within gtk_entry_completion_clear().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk_entry_completion_set_text_column() always added a cell renderer,
regardless of whether there was an existing one already installed. This
patch reuses an old renderer if it exists, but only if it was added by a
previous call to this function.
To avoid conflicts, all renderers that were added manually are removed
when calling this function. Also, the renderer added by this function is
removed when manually adding new renderers. This effectively gives
GtkEntryCompletion two modes (managed and manual cell renderers) and
allows seamless switching between the two.
This is a minor API break. However, this shouldn't be an issue in
practice as applications couldn't call set_text_column() more than once
because of this bug. Also, it is unlikely that many applications mix
set_text_column() and custom cell renderers. The interaction between the
two modes was erratic and not documented well.
https://bugzilla.gnome.org/show_bug.cgi?id=635499
|
|
|
|
| |
To test with Raleigh much easier.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Call gtk_entry_completion_set_text_column() when setting the
"text-column" property directly.
The completion appeared empty when setting "text-column" directly (for
example from a GtkBuilder file), because the setter creates and adds the
GtkCellRendererText.
https://bugzilla.gnome.org/show_bug.cgi?id=710533
|
|
|
|
| |
This can happen if the child has a margin, for instance.
|
|
|
|
|
| |
... that the allocation magic here is for the transition of the
last visible child that's sliding out.
|
|
|
|
| |
GtkBin now handles this for us.
|
| |
|
|
|
|
|
|
| |
Clearing the model in a GtkTreeSelection::changed handler was
crashing. While it is not a 100% kosher thing to do, lets be
more robust here.
|
|
|
|
|
|
| |
This reverts commit b3cffb85f39183a83a99e7517191e46bcd744749.
Pushed by accident.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=710987
|
|
|
|
|
|
| |
Use the new gtk-shell APIs available in mutter to add support for this.
https://bugzilla.gnome.org/show_bug.cgi?id=710056
|
|
|
|
|
| |
This makes it a lot more convenient for developers, as they don't
have to look up the numeric value of response IDs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
_gtk_widget_draw_internal() was clipping by passing the subwindow
sizes as a path to cairo_clip(). This was breaking for windows
larger than 23 bits in width/height, due to cairo using fixed point
(24.8) for the path coordinates.
We fix this by pre-clipping the subwindow region to the existing
cairo clip region in the full 32bit gdkwindow precision. This fixes
the GooCanvas Large Items test.
https://bugzilla.gnome.org/show_bug.cgi?id=710958
|
|
|
|
|
|
| |
This reverts commit e4bb02f8ae698facc204c616108cc8f4c3b579bc.
Responses don't have to be negative.
|
|
|
|
|
|
|
|
|
|
| |
I have been convinced that it is a bad idea to change the behaviour
at the same time as deprecating it, so go back to respecting the
Gtk/ButtonImages xsetting in buttons created with
gtk_button_new_from_stock() when it is set.
The setting as well as the function are still deprecated, and the
default value of the setting will remain FALSE.
|
|
|
|
|
|
|
|
|
| |
I have been convinced that it is a bad idea to change the behaviour
at the same time as deprecating it, so go back to respecting the
Gtk/MenuImages xsetting in GtkImageMenuItem when it is set.
The setting as well as the widget are still deprecated, and the
default value of the setting will remain FALSE.
|
|
|
|
| |
This reverts commit 588ffa8c3241eff2f8e2d99b911a6bcb539347bd.
|
|
|
|
| |
This reverts commit 1b839d4b72a2cedb2bb633b5acd57239860693f4.
|
|
|
|
| |
This reverts commit 7fa27dff259ad79d5a4364d7eaa6b63150082af3.
|
|
|
|
|
|
| |
Instead of hardcoding it in the dnd drop targets list.
Part of bug 707679
|
|
|
|
|
|
|
| |
Make GtkPlacesSidebar also open locations when hovered by
text dnd targets.
Part of bug 707679
|
|
|
|
|
|
|
| |
Make GtkPlacesSidebar also change locations when hovered
by XDS dnd targets (eg. dragging a file from file-roller).
Part of bug 707679
|
|
|
|
| |
Responses need to be negative
|
|
|
|
|
|
|
|
|
| |
The tick callback IDs from GtkWidget aren't timeouts, so
use the correct function to disconnect from them.
Spotted by Benjamin Otte <otte@redhat.com>
https://bugzilla.gnome.org/show_bug.cgi?id=710666
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some widgets, like GtkTreeView, which setup a clock frame
update during realize, it was possible to call
gdk_frame_clock_begin_updating() twice, but only ever disconnecting
from it once. This happens because the realized flag is set at an
unpredictable time by the GtkWidget's realize implementation.
Keep the signal handler ID from us connecting to the "update" signal
to avoid connecting to it twice.
This fixes high wake-up count from any application using GtkTreeView,
even idle ones.
https://bugzilla.gnome.org/show_bug.cgi?id=710666
|
|
|
|
|
|
|
| |
Add names to every timeout we setup, so it's easier to track their
usage, and debug possible misbehaviour.
https://bugzilla.gnome.org/show_bug.cgi?id=710651
|
|
|
|
|
|
|
| |
This is what we used to get through the Net/FallbackIcontheme
setting. Nobody has ever set this setting to a different value,
and people have come to rely on GTK+ applications getting their
icons this way.
|
|
|
|
|
|
| |
The objective is simplify the semantics of the code so that we don't
need to check for "(iter != NULL && !g_sequence_iter_is_end (iter))"
in the callers.
|
|
|
|
|
| |
Otherwise, showing an empty GtkFlowBox will lead to:
GLib-CRITICAL **: g_sequence_get: assertion '!is_end (iter)' failed
|