Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | css: Clipping changes don't need a queue_allocate() anymore | Benjamin Otte | 2018-04-09 | 6 | -13/+10 |
| | | | | | | | | Now that queue_draw() isn't restricted to clip anymore, we don't need to care about clip in the CSS engine either. We do keep GTK_CSS_AFFECTS_CLIP around though because GtkWindow does care for the window's size. | ||||
* | entry: Stop being activatable | Benjamin Otte | 2018-04-09 | 1 | -6/+0 |
| | | | | | | Activating entries does not do anything. Activate the default widget instead. | ||||
* | widget: Don't do a 0-size check before snapshotting | Benjamin Otte | 2018-04-09 | 1 | -2/+1 |
| | | | | | | | Even widgets with an empty allocation may still want to draw stuff. Examples include shadows or child widgets with negative margins. Fixes GtkEntry's progressbar not showing up anymore. | ||||
* | ModelButton: Use WARN_INVALID_PROPERTY, not assert | Daniel Boles | 2018-04-08 | 1 | -2/+4 |
| | | | | Do the same thing we do everywhere else for invalid properties. | ||||
* | ModelButton: Fix type Wether => Whether | Daniel Boles | 2018-04-08 | 1 | -1/+1 |
| | |||||
* | ModelButton: Protect against nonsensical gbooleans | Daniel Boles | 2018-04-08 | 1 | -0/+4 |
| | | | | the same way we do normally. | ||||
* | listbox: Fix signal name in documentation | Mohammed Sadiq | 2018-04-08 | 1 | -1/+1 |
| | |||||
* | Fix some g-i annotation warnings | Rico Tzschichholz | 2018-04-06 | 4 | -5/+5 |
| | |||||
* | menu: Avoid an invalid read | Timm Bäder | 2018-04-06 | 1 | -6/+7 |
| | |||||
* | lockbutton: Remove priv pointer | Timm Bäder | 2018-04-06 | 2 | -19/+16 |
| | |||||
* | video: Add autoplay and loop boolean properties | Benjamin Otte | 2018-04-06 | 2 | -0/+147 |
| | |||||
* | gtkmenushell: Port to using GtkEventControllerKeywip/carlosg/kill-event-signals2 | Carlos Garnacho | 2018-04-05 | 2 | -23/+34 |
| | |||||
* | gtkcellrendereraccel: Port to using GtkEventControllerKey | Carlos Garnacho | 2018-04-05 | 1 | -17/+29 |
| | |||||
* | gtkentry: Use key controller to track focus changes | Carlos Garnacho | 2018-04-05 | 1 | -14/+4 |
| | |||||
* | gtkcalendar: Use key controller to track focus changes | Carlos Garnacho | 2018-04-05 | 1 | -20/+19 |
| | |||||
* | gtktextview: Use key controller for focus changes | Carlos Garnacho | 2018-04-05 | 1 | -23/+6 |
| | |||||
* | gtkeventcontrollerkey: Add ::focus-in/out signals | Carlos Garnacho | 2018-04-05 | 1 | -0/+28 |
| | | | | And handle GDK_FOCUS_CHANGE events in order to emit those. | ||||
* | gtkeventcontrollerkey: Add get_group() call | Carlos Garnacho | 2018-04-05 | 2 | -0/+15 |
| | | | | | Callers can use this function on a key-pressed/released signal to find out the key event group, useful in a few places. | ||||
* | gtkmenu: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 2 | -19/+8 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkiconview: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 2 | -25/+19 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkcellrendererspin: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -12/+21 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | appchoooserdialog: use search bar key capture API | Carlos Garnacho | 2018-04-05 | 1 | -13/+3 |
| | |||||
* | inspector: Use search bar API to capture key events from the toplevel | Carlos Garnacho | 2018-04-05 | 3 | -17/+18 |
| | |||||
* | gtksearchbar/entry: Add [gs]et_key_capture_widget() API calls | Carlos Garnacho | 2018-04-05 | 5 | -47/+291 |
| | | | | | This lets these widgets actively pull events from a widget, instead of passively being fed events. | ||||
* | gtkwindow: Perform key activation in gtk_main_do_event() | Carlos Garnacho | 2018-04-05 | 2 | -21/+4 |
| | | | | | | In a similar spirit to the previous commit, make window shortcut activation happen by default on toplevels, without relying on legacy controllers. | ||||
* | gtkwidget: Activate key bindings through run_controllers() | Carlos Garnacho | 2018-04-05 | 1 | -2/+7 |
| | | | | | | | Deferring a bit further making those a standalone controller, make binding activation happen on run_controllers(), so it happens by default on widgets (unless the key event was consumed earlier) without the need of a legacy event controller. | ||||
* | gtkwidget: Break early if non-gesture controllers handle the event | Carlos Garnacho | 2018-04-05 | 1 | -0/+7 |
| | | | | | | | Non gesture controllers have no means to collaborate with other controllers, thus should be considered standalone entities. It makes no sense to propagate any further if scroll/key controllers handled the event. | ||||
* | eventcontrollerkey: Add function to forward stuff elsewhere | Carlos Garnacho | 2018-04-05 | 2 | -1/+24 |
| | |||||
* | gtkmain: Don't use special paths for key event propagation | Carlos Garnacho | 2018-04-05 | 2 | -72/+12 |
| | | | | | Set the event_widget to the window focus, and let event capture/bubble handling do the rest. | ||||
* | gtkrange: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -15/+19 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkcellrendereraccel: simplify grabbing code | Carlos Garnacho | 2018-04-05 | 1 | -15/+16 |
| | |||||
* | combo box: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 2 | -17/+20 |
| | | | | Switch to using ::event. | ||||
* | app chooser: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 1 | -6/+9 |
| | | | | For now, just switch to using ::event. | ||||
* | gtkentrycompletion: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 2 | -10/+17 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkplacessidebar: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -50/+52 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtktextview: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -66/+47 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkflowbox: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -12/+16 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkentry: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -78/+55 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkcolorswatch: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -10/+12 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkcolorplane: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -9/+13 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | gtkcalendar: Stop using ::key-press-event | Carlos Garnacho | 2018-04-05 | 1 | -10/+19 |
| | | | | Use GtkEventControllerKey for the task | ||||
* | Shortcuts window: stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 1 | -7/+16 |
| | | | | Use a key event controller instead. | ||||
* | color editor: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 2 | -12/+26 |
| | | | | Use key event controllers instead. | ||||
* | about dialog: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 2 | -11/+20 |
| | | | | Use a key event controller instead. | ||||
* | places view: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 2 | -34/+32 |
| | |||||
* | inspector: Stop using ::key-press-event | Matthias Clasen | 2018-04-05 | 4 | -43/+74 |
| | |||||
* | docs: Modernize an example | Matthias Clasen | 2018-04-05 | 1 | -28/+14 |
| | | | | The signals that are showcased here are going away. | ||||
* | file chooser: Use a key event controller | Matthias Clasen | 2018-04-05 | 2 | -24/+35 |
| | | | | We want to get rid of ::key-press-event. | ||||
* | gtk: Add GtkGestureStylus | Carlos Garnacho | 2018-04-05 | 7 | -1/+455 |
| | | | | | | This is a GtkGesture done to deal with stylus events from drawing tablets. Those have a special number of characteristics that extend a regular pointer, so it makes sense to wrap that. | ||||
* | gtkwindow: Unset focus grab_widget if it ends up unmapped | Carlos Garnacho | 2018-04-05 | 1 | -0/+5 |
| | | | | | | This may result on the later emission of crossing events, with one of the sides being already unmapped/unrealized. The widget being unmapped will result on repick and emission of a set of crossing events anyway. |