| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
In 99.9% of all cases, these are just NULL, NULL.
So just do away with these arguments, people can
use the setters for the rare cases where they want
the scrolled window to use a different adjustment.
|
|
|
|
|
|
| |
Change gtk_widget_translate_coordinates and
gtk_native_get_surface_transform to operate
on doubles. Update all callers.
|
|
|
|
| |
These are all on GtkBox or enumerating children.
|
|
|
|
| |
Stop using child properties and margin property.
|
|
|
|
|
| |
Replace all uses of gtk_container_add on overlays
by gtk_overlay_set_child.
|
|
|
|
|
| |
Replace all uses of gtk_container_add on windows
by gtk_window_set_child.
|
|
|
|
|
| |
Replace all uses of gtk_container_add on popovers
by gtk_scrolled_window_set_child.
|
|
|
|
|
|
| |
Replace most uses of gtk_style_context_add/remove_class
by the new APIs. The only remaining uses of the old API
are in save/restore situations.
|
|
|
|
|
|
| |
And fix all the errors and warnings resulting from that
See #2491
|
|
|
|
| |
Trying to get the ci style test to pass.
|
|
|
|
| |
Replace it with margin-start, -end, -top, -bottom throughout.
|
| |
|
|
|
|
| |
Replace these calls with direct use of GMainContext api.
|
|
|
|
|
| |
Rename the can-pick property to can-target,
and redo the pick flags with more descriptive names.
|
|
|
|
|
| |
Use gtk_widget_set_can_pick instead of the
overlay-specific api with the same purpose.
|
| |
|
|
|
|
| |
It might soon go away!
|
|
|
|
| |
Accidentally disabled in 8b14c8d0a820e6617bd72a39a53d2ae6fa7b242b
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We have this information available in enter events,
and having it in the controller signal as well makes
porting easier.
Update existing users.
|
|
|
|
|
| |
We can stop using ::enter-notify-event here, and use
our new motion event controller instead.
|
| |
|
|
|
|
|
| |
The intent is detecting enter events into the overlayed label, so just
connect to ::enter-notify-event on the label with no GdkWindow checks.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We now rely on toplevels receiving and forwarding all the events
the windowing should be able to handle. Event masks are no longer a
way to determine whether an event is deliverable ot a widget.
Events will always be delivered in the three captured/target/bubbled
phases, widgets can now just attach GtkEventControllers and let those
handle the events.
|
|
|
|
| |
GtkWidget:halign and GtkWidget:valign are sufficient
|
|
|
|
| |
GtkWidget already has hexpand/vexpand properties.
|
| |
|
|
|
|
| |
Adapt all our tests and examples to the new initialization api.
|
|
|
|
| |
People should use the GtkCssProvider::parsing-error signal instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
The API to access this functionality will be the setter we just added in
the previous commit.
https://bugzilla.gnome.org/show_bug.cgi?id=750568
|
| |
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750568
https://bugs.freedesktop.org/show_bug.cgi?id=90917
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750568
https://bugs.freedesktop.org/show_bug.cgi?id=90917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this case we have a bunch of interactive main children
of the overlay, and then a centered overlay that contains both
non-interactive (labels) and interactive (entry) widgets.
This shows off a problem where the non-interactive parts (the labels)
steals input from the overlay main children (breaks button click and
hover effects).
https://bugzilla.gnome.org/show_bug.cgi?id=750568
https://bugs.freedesktop.org/show_bug.cgi?id=90917
|
|
|
|
|
| |
It's the last test still spewing these and I'm too lazy to do a proper
fix.
|
|
|