| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The previous code ordered them the wrong way, so the first button (from
a CSS pov) was the last visible one.
|
|
|
|
|
|
| |
We must call get_preferred_width/height on the slider buttons
before allocating them, otherwise the layout machinery spews
warnings.
|
|
|
|
| |
Instead of the custom get_path_for_child() function.
|
|
|
|
|
|
|
|
|
| |
Changing the visibility of child widgets in size-allocate does
not work well with out current allocation and layout machinery.
To avoid the visual fallout, just keep the arrow buttons visible
and only change their sensitivity.
https://bugzilla.gnome.org/show_bug.cgi?id=754868
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=757269
|
|
|
|
|
|
|
|
| |
The current icon handling did not update icons for widget
state changes, causing black-on-black icons in HighContrast.
Instead, use the GIcon.
https://bugzilla.gnome.org/show_bug.cgi?id=753397
|
| |
|
|
|
|
|
|
|
|
| |
The file chooser code now calls into the path bar in init,
starting an async operation. This unveiled that the path bar
code was not safe against being disposed early, by causing
a crahsh of the objects-finalize test.
Fix this by making the callback check for CANCELLED.
|
| |
|
|
|
|
| |
The theme will be changed to provide padding.
|
|
|
|
|
| |
We were only recreating the icons the very first time the theme
changed, and not every time as was intended.
|
|
|
|
|
| |
This fits better with the symbolic icons we use in the places
sidebar now.
|
|
|
|
|
| |
Set text-button/image-button on these, just like we do for
buttons everywhere else.
|
|
|
|
|
| |
This will allow nautilus to reuse the style on its own
pathbar widget.
|
|
|
|
| |
.. so the path bar's buttons can have shadows.
|
|
|
|
| |
This was just an unneeded include anyway.
|
| |
|
| |
|
|
|
|
|
| |
Otherwise, we are at the mercy of the container giving us
more space than we request, which does not always work.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
So that it's always linked with the rest of the pathbar.
https://bugzilla.gnome.org/show_bug.cgi?id=706722
|
|
|
|
|
|
| |
It's always zero.
https://bugzilla.gnome.org/show_bug.cgi?id=706722
|
|
|
|
|
|
| |
This is closer to the nautilus path bar.
https://bugzilla.gnome.org/show_bug.cgi?id=706451
|
|
|
|
|
|
|
| |
This was accidentally removed in commit
42f53ab58e3f905b242029c2ea446d79d2113725
https://bugzilla.gnome.org/show_bug.cgi?id=706028
|
|
|
|
|
|
|
|
|
|
|
| |
We rename the gtk_widget_class_bind_template_child{_internal}
macros by appending a _private to their name. Otherwise, it
would be too magic to pass the 'public' names as arguments,
but affect a member of the Private struct. At the same time,
Add two new macros with the old names,
gtk_widget_class_bind_template_child{_internal} that operate
on members of the instance struct.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The macros and functions are inconsistently named, and are not tied to
the "template" concept - to the point that it seems plausible to use
them without setting the template.
The new naming scheme is as follows:
gtk_widget_class_bind_template_child_full
gtk_widget_class_bind_template_callback_full
With the convenience macros:
gtk_widget_class_bind_template_child
gtk_widget_class_bind_template_child_internal
gtk_widget_class_bind_template_callback
https://bugzilla.gnome.org/show_bug.cgi?id=700898
https://bugzilla.gnome.org/show_bug.cgi?id=700896
|
|
|
|
|
|
|
|
|
|
| |
Using an offset from the struct means you can have children in
both the public and private (via G_PRIVATE_OFFSET) parts of the
instance. It also matches the new private macros nicer.
https://bugzilla.gnome.org/show_bug.cgi?id=702563
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
| |
Drop includes of deprecated headers where they are
no longer needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We've recently a number of classes wholly. For these cases,
move the headers and sources to gtk/deprecated/ and adjust
Makefiles and includes accordingly.
Affected classes:
GtkAction
GtkActionGroup
GtkActivatable
GtkIconFactory
GtkImageMenuItem
GtkRadioAction
GtkRecentAction
GtkStock
GtkToggleAction
GtkUIManager
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
| |
|
|
|
|
|
| |
We want to use GtkIconTheme instead. It is worth noting that
the parts that remain undeprecated are GtkIconSize and gtk_icon_size_lookup.
|
|
|
|
|
| |
We don't have icons rendered at arbitrary sizes and we have better
APIs that aren't restricted to GtkIconSizes.
|
| |
|
|
|
|
|
|
|
|
| |
Deprecate gtk_widget_push_composite_child, gtk_widget_pop_composite_child,
gtk_widget_set_composite_name, gtk_widget_get_composite_name.
This API is just bloat and was never useful, this patch deprecates
it and removes all internal calls to the composite child APIs
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the previously hardcoded calls to gdk_window_set_user_data,
and also lets us track which windows are a part of a widget. Old code
should continue working as is, but new features that require the
windows may not work perfectly.
We need this for the transparent widget support to work, as we need
to specially mark the windows of child widgets.
https://bugzilla.gnome.org/show_bug.cgi?id=687842
|
|
|
|
|
| |
We need to update the child pointer to the current iterator when going
trough the button list.
|
|
|
|
|
| |
I still don't like queueing restyles in size_allocate(), but I can't
come up with a better mechanims for the way the pathbar works today.
|
|
|
|
|
|
| |
Add an internal API that allows GtkStyleContext to create a widget path
for the widget and with that bypassing gtk_widget_get_path() and that
function caching the path.
|
|
|
|
| |
Instead of resetting them completely
|
|
|
|
| |
and include them in the C files instead.
|
|
|
|
|
|
|
| |
In particular gtksettings.h and gtkstylecontext.h needed to be included
in lots of places now.
Also, I order the includes alphabetically in a bunch of headers.
|
|
|
|
|
| |
We need to select for scroll events on the buttons now, selecting
for button events no longer gives us scrolling as a side-effect.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
It used to be that _gtk_path_bar_set_file() would return an error if
it wasn't able to switch to the specified file, but that hasn't been
the case for a long while now, since the file chooser became async.
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|
|
|
|
| |
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|