| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first step towards refactoring how widgets deal with event
controllers.
In the future, the widget will treat controllers the same way it treats
child widgets:
1. The controllers will be created without a widget.
2. There will be gtk_widget_add/remove_controller() functions to add
or remove controllers.
3. The widget will hold a reference to all its controllers.
This way we will ultimately be able to automate controllers with ui
files.
|
| |
|
|
| |
This is unchecked, we can remove it entirely as well.
|
| |
|
|
|
|
| |
It might not be entirely clear what the boolean return value means.
https://bugzilla.gnome.org/show_bug.cgi?id=770026
|
| |
|
|
|
|
|
| |
This will be used right before handle_event() in order to filter
out events, useful to make the previous "no touchpad events" behavior
the default, and have gesture subclasses include manually the touchpad
events they handle.
|
| |
|
|
|
| |
This will rarely have any use if no subclassing is allowed, so just make it
private for our own.
|
|
|
For now, at least. We do this by hiding the instance and
class structures in private headers.
|
