| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
When we are reallocating widgets, make sure that
we get a motion event in the next frame cycle,
so the hover state gets updated.
|
|
|
|
|
|
|
| |
We want to ensure that the pointer position is reflected
when widget geometry changes, so add a function that tells
GDK "please create a motion event at the current position
on this surface, if one doesn't happen already".
|
|\
| |
| |
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!2488
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
We need to look a the position, not the child surface.
|
| |
| |
| |
| |
| | |
Now that this is backend-only api, we can just
drop unused arguments.
|
| |
| |
| |
| | |
We need to look a the position, not the child surface.
|
| |
| |
| |
| |
| | |
Now that this is backend-only api, we can just
drop unused arguments.
|
| |
| |
| |
| | |
We need to look a the position, not the child surface.
|
| |
| |
| |
| |
| | |
Now that this is backend-only api, we can just
drop unused arguments.
|
| |
| |
| |
| | |
We need to look a the position, not the child surface.
|
| |
| |
| |
| | |
It is no longer used.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Just call the backend implementation directly.
|
| |
| |
| |
| | |
Just call the backend implementation directly.
|
| |
| |
| |
| | |
It is now unused.
|
| |
| |
| |
| | |
Directly use the backend implementation.
|
| |
| |
| |
| | |
Directly use the backend implementation.
|
|/
|
|
| |
Directly use the backend implementation.
|
|\
| |
| |
| |
| |
| |
| | |
Matthiasc/for master
Closes #3090
See merge request GNOME/gtk!2485
|
| |
| |
| |
| |
| |
| |
| | |
A year ago, we make this function not return the child
surface anymore. But the information whether the device
is actually over the surface is still useful, and we
should not loose it.
|
| |
| |
| |
| |
| |
| |
| |
| | |
We are reusing the GtkCrossingData struct for multiple
calls here, so we need to make sure that the targets
stay alive from beginning to end.
Fixes: #3090
|
| |
| |
| |
| |
| |
| | |
We need to make sure that the crossing data stays
alive until we are done handling it, so take references
on all the widgets in it.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
broadway: Prune fully clipped render nodes
Closes #3086
See merge request GNOME/gtk!2487
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If some node is fully outside the clip region we don't send it to the daemon.
This helps a lot in how much data we send for scrolling viewports.
However, sending partial trees makes node reuse a bit more tricky. We
can't save for reuse any node that could possibly clip different depending on
the clip region, as that could be different next frame. So, unless the
node is fully contained in the current clip (and we thus know it is not
parial) we don't allow reusing that next frame.
This fixes #3086
|
| | |
| | |
| | |
| | |
| | | |
If we know what can't possibly be visible we may can later decide to
not expose a node.
|
|/ / |
|
|\ \
| |/
|/|
| |
| | |
Broadway: Fix handling of debug nodes
See merge request GNOME/gtk!2486
|
| |
| |
| |
| |
| | |
The debug nodes have id BROADWAY_NODE_DEBUG, which happens to be "12".
So, don't hardcode the wrong number "14".
|
|\ \
| |/
|/|
| |
| | |
broadway: Correct handling of opaque colors
See merge request GNOME/gtk!2484
|
|/
|
|
|
|
| |
If alpha is 255, we use rgb() instead of rgba(), not if alpha is 0.
This makes the title bar gradient go from fully transparent to blue
rather than black to blue..
|
|\
| |
| |
| |
| | |
fontchooser: Populate the list incrementally
See merge request GNOME/gtk!2483
|
| |
| |
| |
| |
| |
| |
| | |
By adding 20 fonts / frame to the font list, we can
get the font chooser dialog to show up much faster.
This change gets the font chooser up in 265ms here.
|
|\ \
| | |
| | |
| | |
| | | |
Ebassi/for master
See merge request GNOME/gtk!2480
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We cannot pass all the data we pass to the virtual function, because the
types are private, but the class and the signal are public API.
The signal is just a notification, so we can decouple the virtual
function (which stays the same, for internal types that implement the
ATContext API contract) from the signal.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The variadic arguments methods cannot be used by language bindings,
which means we can let them use their names when calling the
GValue-based methods.
|
| | |
| | |
| | |
| | | |
Use a gtk-doc stanza, instead of the GParamSpec strings.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the ATContext state hasn't changed—for instance, if the accessible
attributes have been set to their default value, or have been set to the
same value—do not emit an accessible state change. State changes can be
arbitrarily expensive, so we want to ensure that they are meaningful.
|
| | |
| | |
| | |
| | | |
We can use that information inside the ATContext.
|
| | | |
|
| | |
| | |
| | |
| | | |
Like we do for the varargs API.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bail out early, instead of going deep into the GtkAccessibleValue type
equal() implementation, where we expect both accessible values to have
the same type.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gtk-demo: Avoid double borders
See merge request GNOME/gtk!2478
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Replace the frame with a separator.
|