| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Use the helper function we have for this, don't do it manually. This has
the side effect of also supporting icon transforms.
|
|
|
|
|
|
|
|
|
| |
Yes, I like playing around. To enjoy, add this CSS to your application
of choice (preferrably glade or something with lots of images):
GtkImage { animation: spin 2s linear infinite; }
You can thank me later.
|
|
|
|
| |
Just like normal icons, icon surfaces belong into gtkrendericon.c.
|
| |
|
|
|
|
|
|
|
|
|
| |
The spinner is a regular builtin image now. There is no need to go
through the shadows code manually anymore as regular items do get
shadows automatically.
This also allows simplifying the actual spinner drawing code so that it
actually works.
|
|
|
|
|
| |
This not only reduces code, but also allows for builtin images to have
shadows or be transformed using -gtk-icon-transform.
|
|
|
|
|
| |
Instead, make the buiultin image get those properties itself in the
compute vfunc.
|
|
|
|
|
|
|
|
| |
The order in which properties are defined depends on the order in which
they are computed. And that means that properties can only depend on
other properties that are defined before them.
The next patches will need this reordering.
|
|
|
|
|
|
|
|
| |
Instead of supporting every angle, just support top, right, bottom and
left and round the angle to one of those directions.
Adwaita overrides arrows anyway and doesn't even look at the angle, so
this should not be a problem.
|
|
|
|
|
| |
Instead, split the grip into 8 different builtin images (one for each
side and corner).
|
|
|
|
|
| |
We add to the enum to account for the images generated for different
states.
|
|
|
|
|
|
|
|
| |
Also, make it have a generic entry point with
gtk_css_image_builtin_draw().
The only feature lost so is the drawing of shadows for spinners, but
that will come back later.
|
| |
|
|
|
|
|
| |
As a side effect, we can use _gtk_css_section_to_string() to format the
section and save a lot of code.
|
| |
|
|
|
|
|
|
| |
gtkrenderborder.c now contains the implementation for
gtk_css_style_render_border
gtk_css_style_render_outline
|
| |
|
|
|
|
| |
I want the gtkrender prefix for all filenames about rendering.
|
| |
|
|
|
|
| |
I want the gtkrender prefix for all filenames about rendering.
|
|
|
|
| |
... and move the whole function into gtkthemingbackground.c
|
| |
|
| |
|
|
|
|
|
| |
This is in preparation for iusing GtkCssStyle instead of GtkStyleContext
in render functions.
|
|
|
|
|
| |
The name now better reflects what it does, since GtkCssComputedValues
was renamed to GtkCssStyle, too.
|
|
|
|
| |
Unset all CSS; Adwaita was messing up things.
|
|
|
|
|
|
|
| |
Overriding the window background is ugly because the window background
is owned by GTK and can be reset at any time.
https://bugzilla.gnome.org/show_bug.cgi?id=742646
|
|
|
|
|
|
|
| |
This is necessary since we do the new caching and need to distinguish
between styles with different IDs.
Fixes various test cases.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This looks odd in combination with the top underflow.
|
|
|
|
|
|
| |
These are retrieved from XInput device properties.
https://bugzilla.gnome.org/show_bug.cgi?id=740758
|
|
|
|
|
|
|
| |
These are a construct only properties, expected to be filled in from
platform specific code.
https://bugzilla.gnome.org/show_bug.cgi?id=740758
|
|
|
|
|
|
|
|
|
| |
When removing all rows, trying to add rows would not work
and throw criticals. This is fallout from a recent change
to insert rows at the right position. Fix this by handling
the 'empty model' case separately.
https://bugzilla.gnome.org/show_bug.cgi?id=743157
|
|
|
|
|
|
|
|
|
|
| |
This was left unmodified when GtkScrolledWindow was made a windowed widget.
Displacing here by the widget allocation is not necessary anymore, since
we are invalidating the window set at these coordinates.
This patch is a simplification of a previous one by Timm Bäder.
https://bugzilla.gnome.org/show_bug.cgi?id=742243
|
|
|
|
|
| |
Introduced in e649c8773f0357df19f4e28aabf40a203a39c409. It's obviously
the root node right there.
|
| |
|
|
|
|
|
| |
Better to switch the visible stack child early, since GtkStack
has its own focus handling now.
|
|
|
|
|
|
|
|
|
|
|
| |
GtkImageMenuItem always packs a GtkImage when it is synced with a
related action. This is unnecessary when the action doesn't have an icon
set and results in excess padding when a GtkImageMenuItem is put in a
menu bar (GtkUIManager does this).
Fix this by not creating the GtkImage for icon-less actions.
https://bugzilla.gnome.org/show_bug.cgi?id=742181
|
|
|
|
| |
Use _gtk_style_context_peek_property() instead.
|
|
|
|
| |
Use _gtk_style_context_peek_property() instead.
|
|
|
|
|
|
|
| |
Just add a 3rd stop in the place where the gradients for the other
states have a 3rd stop. When running transitions between states, this
avoids cross-fades and instead uses the much faster gradient
transitioning code.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of asserting, just print a g_warning() and try to work around
the problem.
I hope that g_warning() isn't too spammy for people that are hit with
it.
Also clarify the docs that not restore()ing after a save() is a bad
idea.
https://bugzilla.gnome.org/show_bug.cgi?id=743101
|
|
|
|
|
|
| |
When creating the query path, explicitly specify if it's for a root node
or for a child. Relying on gtk_style_context_is_saved() is unreliable
(for example when updating the cache).
|
|
|
|
|
|
|
| |
The last round of filechooser redesign work had left
search somewhat dysfunctional. This commit fixes things
up enough that search is once again a working feature
of the file chooser.
|