| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This function is a convenience wrapper around
gtk_button_new() and gtk_button_set_image().
https://bugzilla.gnome.org/show_bug.cgi?id=705918
Signed-off-by: Yosef Or Boczko <yoseforb@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes:
(rhythmbox:22802): Gtk-CRITICAL **:
_gtk_widget_get_preferred_size_for_size: assertion 'size >= -1' failed
that is gtk_paned_get_preferred_size_for_opposite_orientation calls
_gtk_widget_get_preferred_size_for_size on child2 with a negative
size.
As gtkpaned size was (32), child1 minimum size was (55) then
for_child1 became (32) for an handle_size of (5). Thus for_child2
ended up as (-5).
https://bugzilla.gnome.org/show_bug.cgi?id=705624
|
|
|
|
|
|
|
|
| |
Just as for GtkRangeAccessible, we were not even trying to disconnect
the signal handler from the adjustment. The same fix works here:
override the widget_set and widget_unset vfuncs.
https://bugzilla.gnome.org/show_bug.cgi?id=705692
|
|
|
|
|
|
|
|
|
| |
We were only disconnecting the signal in finalize, when
the widget was already unset. Instead, override the widget_set
and widget_unset vfuncs of GtkAccessible, and keep a reference
to the adjustment.
https://bugzilla.gnome.org/show_bug.cgi?id=705692
|
| |
|
|
|
|
|
|
| |
Don't point to a replacement that is itself deprecated.
https://bugzilla.gnome.org/show_bug.cgi?id=705372
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=705524
|
|
|
|
|
|
|
|
| |
Replace the deprecated API calls with the updated APIs, and fix the build
of modules/input/gtkimcontextime.c, as we really needed
gdk/gdkkeysyms-compat.h (gdk/gdkkeysyms.h was already included)
https://bugzilla.gnome.org/show_bug.cgi?id=705068
|
|
|
|
|
|
|
| |
The default middle-click action on the titlebar should be to lower
the window. Implement that.
https://bugzilla.gnome.org/show_bug.cgi?id=705809
|
|
|
|
|
| |
These were reported missing in bug
https://bugzilla.gnome.org/show_bug.cgi?id=705672
|
|
|
|
|
|
|
| |
Make sure we always deal with the same screen when
connecting / disconnecting the theme-variant changed handler.
Pointed out by Morten Welinder in
https://bugzilla.gnome.org/show_bug.cgi?id=705640
|
|
|
|
|
|
|
|
| |
When bookmarks are long, the file chooser button would
grow too much. This can be avoided by ellipsizing.
Patch by Ritesh Khadgaray,
https://bugzilla.gnome.org/show_bug.cgi?id=672220
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an icon is requested as symbolic, our generic fallback algorithm
uses fullcolor icons when the specified icon name is not found, treating
the "-symbolic" suffix as another component of the icon name.
Change the algorithm to check beforehand if the icon is symbolic, remove
the suffix if so, and re-add it at the end for all the generated icon
names.
https://bugzilla.gnome.org/show_bug.cgi?id=680926
|
|
|
|
|
|
|
| |
This allows CSD windows to be maximized, tiled, and constrained
properly.
https://bugzilla.gnome.org/show_bug.cgi?id=705765
|
|
|
|
| |
.. and clean up code
|
| |
|
|
|
|
|
|
|
|
| |
With multiple GDK backends in the process, we run into problems where
we try to use the Wayland im module on X, which crashes. This commit
adds a quick backend filter that removes the wayland, xim and ime
input methods from consideration unless the corresponding GDK backend
is in use.
|
|
|
|
|
|
|
|
|
| |
This code is called early on, without a window, and then later on
with a window. Currently, it returns different results for these
cases when the setting contains a value. That leads to pointless
construction and destruction of im contexts. Instead, just look
at the settings of the default screen. In practice, there is only
one screen, ever.
|
| |
|
|
|
|
|
|
|
| |
This just moves the gtk_list_box_insert function to where the rest of the
public API is defined.
https://bugzilla.gnome.org/show_bug.cgi?id=705558
|
|
|
|
|
|
|
| |
... to make it possible to insert rows in the middle of the list without having
to fiddle with the sort functions. One of the first users is going to be Glade.
https://bugzilla.gnome.org/show_bug.cgi?id=705558
|
|
|
|
|
|
| |
This makes the icon view look completely seamless when dragging.
https://bugzilla.gnome.org/show_bug.cgi?id=705605
|
|
|
|
|
|
|
| |
This doesn't look good when combined with rounded corners on
selected items.
https://bugzilla.gnome.org/show_bug.cgi?id=705605
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=705601
|
|
|
|
| |
This allows things to correctly scale things on HiDPI screens.
|
| |
|
|
|
|
|
|
|
| |
Add a convenience method for prepending rows to a list box without
having to fiddle with a sort function.
https://bugzilla.gnome.org/show_bug.cgi?id=705558
|
|
|
|
|
|
| |
It's obvious, but it's better to say it.
https://bugzilla.gnome.org/show_bug.cgi?id=705529
|
|
|
|
|
| |
If we have rgba visuals and a composited screen we should
just use a RGBA window rather than shaped windows.
|
|
|
|
|
|
|
|
| |
To handle hidpi support we need to make sure we don't
downscale scaled css images.
Note: If cairo_surface_create_similar starts doing this
by itself we need to back this out.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A problem with the zoom scroll mode is that you have to restart
if you hit the bottom of the screen before you hit the bottom
of your document.
This commit adds an autoscroll feature to the zoom scroll: if
you move outside the window while in zoom scroll mode, we keep
scrolling in the direction you were going until you let go
of the mouse button.
https://bugzilla.gnome.org/show_bug.cgi?id=704703
|
|
|
|
|
|
|
|
|
|
|
| |
Triggering zoom scroll mode by Shift click was too much
of an easter egg. It also requires using keyboard and
mouse together, which is hard to do for many users.
Instead, we now trigger zoom scroll mode by click-and-hold
(or touch-and-hold).
https://bugzilla.gnome.org/show_bug.cgi?id=704703
|
|
|
|
|
|
|
|
|
|
|
|
| |
The internal class GtkPressAndHold was so far only
reacting to touch events. But in most cases where
a touch-and-hold or 'long press' pattern is useful,
click-and-hold can also be used.
This patch makes GtkPressAndHold react to mouse
clicks as well.
https://bugzilla.gnome.org/show_bug.cgi?id=704703
|
|
|
|
|
|
|
|
| |
Add a boolean property that controls whether a window close button
will be shown in the header bar or not. Doing this in the toolkit
will ensure consistency of the visual apperance.
https://bugzilla.gnome.org/show_bug.cgi?id=702971
|
| |
|
|
|
|
|
| |
A recent refactor of this code missed a check for the wildcarded state
on the icon source.
|
|
|
|
| |
This was found by the clang static analyzer.
|
|
|
|
|
| |
This was missed during the pixbuf->surface conversion, so when the state
changed we were not recreating a new surface for it.
|
|
|
|
|
|
| |
These files are generated, so adding them to git is somewhat
icky, but it helps translators who currently can't use intltool-update
on a fresh git checkout.
|
|
|
|
| |
Make sure the close button is right aligned and centered vertically.
|
| |
|
|
|
|
|
|
| |
Make GtkInfoBar slide in and out as it is shown or hidden.
https://bugzilla.gnome.org/show_bug.cgi?id=704334
|
|
|
|
|
|
|
|
|
| |
Don't specify packing properties for internal children.
This doesn't work unless the internal children are actually
direct children of the container (which we are about to
change for GtkInfoBar). Also, it is redundant, since we
just set the properties to the values they already have
anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Packing properties in ui files are parsed and handled by
the container, which assumes that the child is a direct
descendant. For internal children, this is inconvenient,
because we don't want to reconstruct the entire internal
structure between the container and the child in the ui
file.
It would be best to not specify packing properties
in that case, but since existing ui files do this for
GtkInfoBar and we are about to change the internal
structure of GtkInfoBar, be more forgiving here.
|
|
|
|
|
|
|
| |
This reverts commit 1198ffb0bc195c6044d4d0efd864ccf093d637c7.
This change needs more work, to avoid breaking existing
ui files.
|
|
|
|
|
|
|
| |
This reverts commit fbbcb5c01b5d171ddb1c5f5b298779cfe830c441.
We will be doing this in gnome-settings-daemon itself instead,
as some X11 based platforms using GTK+ will want to override this.
|
| |
|
|
|
|
| |
different recommended sizes
|