| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
We already take ints when setting the translation, so it can't
currently take any other values. Additionally, I was seeing large
costs in int -> double -> int for the rects in
gtk_snapshot_clips_rect(), as all callers really are ints (widget
allocations) and the clip region is int-based.
This change completely cleared a 2% rectangle_init_from_graphene from
the profile and is likely to have nice performance effects elsewhere
too.
|
| |
|
|
|
|
|
|
| |
The width/height/aspect getters are called a lot, and almost all
callers already verify it from _gtk_css_image_get_concrete_size (),
so just skip these checks.
|
| |
|
|
|
|
| |
This avoids a lot of checking overhead.
|
|
|
|
|
| |
Rather than allocate new ones all the time we reuse the previous ones.
We just clear them and save them in the parent for later reuse.
|
|
|
|
|
|
| |
This means we allocate the collect data with the state, avoiding
an extra allocation. Also, a union means every state object
is the same size and we could reuse the state objects.
|
|
|
|
|
| |
Otherwise we do a lot of allocations and vprintf calls which are
not used.
|
|
|
|
|
|
|
|
| |
This was showing up quite high on the profiles, and there is
no real reason for copy to normalize, as the source is a
GskRoundedRect which should be normalized already unless
you did something very strange (and then you should have normalized
manually).
|
|
|
|
|
|
| |
This gets called a lot during snapshotting, and this change
alone brings down snapshot time by almost 10% in a syntethic
snapshot test.
|
| |
|
|
|
|
| |
Not much detail here yet, but the syntax is documented.
|
|
|
|
|
|
|
| |
Simgle image cross-fade opacity was computed the wrong way, which caused
weird fade-in/out animations, for example in flat buttons.
I messed this up when porting cross-fades to snapshot().
|
|
|
|
|
|
| |
Since the demise of theme engines, we can no longer hit
the case of id >= GTK_CSS_PROPERTY_N_PROPERTIES. So don't
check for this in a very frequently called function.
|
|
|
|
|
| |
We should not slow down the core parts of the css machinery
with type checks.
|
|
|
|
|
| |
It seems odd to have checks in just a few functions,
so switch everything over to use the internal versions.
|
|
|
|
| |
This avoids type checks in places where we know it is safe.
|
|
|
|
|
| |
Reshuffling things a bit to avoid a bunch of NULL and
type checks.
|
|
|
|
|
|
|
| |
Using an image() fallback from svg to png doesn't make too
much sense, since the svg is always used (unless librsvg is
not present), while the png icon is faster and cheaper to
load and thus preferable.
|
|
|
|
|
|
|
| |
Since we're a library, crashing on gsettings keys, whose presence is out
of our control, isn't appropriate.
https://bugzilla.gnome.org/show_bug.cgi?id=775846
|
|
|
|
|
|
|
| |
The gsetting was recently added so that we can have this configurable
on the wayland backend too.
https://bugzilla.gnome.org/show_bug.cgi?id=775846
|
| |
|
|
|
|
|
|
| |
Also, "ie" wasn't very clear, but fixing that to "i.e." would cause
truncation of the summary when processed by bindings using doxygen. So,
I replaced it with "in other words", which is no _less_ clear, at least.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=775732
|
|
|
|
|
| |
It was suggested that the project files to be moved to win32/, so that we can
have one less layer of directories we need to go down into to reach the project files.
|
|
|
|
|
|
| |
Tell people about what happens when generating projects when Visual
Studio 2013 or later is required, and mention that the .headers are
only needed when headers need to be copied.
|
|
|
|
|
| |
We were computing it relative to the gadget allocation, but it should be
relative to the widget allocation.
|
| |
|
| |
|
|
|
|
|
|
|
| |
So we can set the css name of a widget to something that's not related
to the class name. If the css-name property is set to NULL, we will
still fall back to the one set using gtk_widget_class_set_css_name which
is alwasys non-NULL since GtkWidget itself sets it to "widget".
|
| |
|
|
|
|
|
| |
So we can show and hide it with a transition as well as bind another
property to it.
|
|
|
|
|
| |
All the style properties in GtkTreeView are gone, so use one from
GtkScrollbar for now.
|
|
|
|
| |
The previous reordering broke the builderparser test case.
|
|
|
|
| |
So we get a proper error message.
|
| |
|
| |
|
|
|
|
|
| |
They only show/hide the widget in a delayed fashion which doesn't
work, just like it doesn't work with infobars and popovers.
|
| |
|
| |
|
|
|
|
| |
They were unused and unimplemented.
|
|
|
|
| |
It's unused in GTK.
|
|
|
|
|
|
|
| |
They are all unused by GTK.
And other people can write their own find functions if they need any in
their tests.
|
|
|
|
|
|
|
|
| |
We currently have various ways to initialize GTK+, and not
all of them were supporting this way of bringing up the
inspector. Fix this.
https://bugzilla.gnome.org/show_bug.cgi?id=776807
|
|
|
|
|
|
| |
Add missing 'test'
https://bugzilla.gnome.org/show_bug.cgi?id=776736
|
| |
|
| |
|
|
|
|
| |
We don't want to expose GdkWindows in the public API.
|
| |
|
| |
|