summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Use NULL for generic marshallers in g_signal_new()Benjamin Otte2016-08-2966-193/+178
| | | | | glib will use the correct marshaller automatically. And as a side effect, we also get all glib optimizations, like a va marshaller.
* about dialog: Set a max-content-height on creditsMatthias Clasen2016-08-291-0/+1
| | | | | | | This keeps the credits section from making the dialog grow when there are lots of credits. https://bugzilla.gnome.org/show_bug.cgi?id=770458
* gtkplacessidebar: fix signal marshalCarlos Soriano2016-08-291-1/+1
| | | | | | | | | | | | We were using __VOID for the SHOW_OTHER_LOCATION signal that uses flags named SHOR_OTHER_LOCATION_WITH_FLAGS. However, if a signal uses flags the marshal needs to use __FLAGS. This patch addresses this using VOID__FLAGS as the marshaler parameter. Thanks to Jan Steffens for pointing this out. https://bugzilla.gnome.org/show_bug.cgi?id=770550
* Updated Serbian translationМирослав Николић2016-08-282-2075/+2331
|
* Updated Serbian translationМирослав Николић2016-08-282-996/+1192
|
* GDK W32: Remove obsolete assertionsРуслан Ижбулатов2016-08-261-2/+0
|
* Updated Polish translationPiotr Drąg2016-08-261-16/+32
|
* UpdatesMatthias Clasen2016-08-261-0/+70
|
* Add braces to appease gccBenjamin Otte2016-08-253-6/+16
| | | | | -ftrack-macro-expansion=0 doesn't like if statements without braces when evaluating indentation levels.
* uimanager: Correctly indent codeBenjamin Otte2016-08-251-10/+10
|
* a11y: Correctly indent codeBenjamin Otte2016-08-251-1/+2
|
* Updated Slovenian translationMatej Urbančič2016-08-251-411/+922
|
* Updated Slovenian translationMatej Urbančič2016-08-251-42/+42
|
* cell renderer text: Allow entries to shrinkMatthias Clasen2016-08-251-0/+1
| | | | | | | Set a small max-width on entries used for editing cells, so they adapt to small columns and don't overlap the next column. https://bugzilla.gnome.org/show_bug.cgi?id=770374
* wayland: add min/max size from xdg-shell v6Olivier Fourdan2016-08-251-0/+36
| | | | Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=764413
* wayland: Implement move_to_rectJonas Ådahl2016-08-251-50/+462
| | | | | | | Translate move_to_rect parameter into xdg_positioner requests, and use the generated xdg_positioner to create the popup. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Port to xdg_shell unstable v6Jonas Ådahl2016-08-254-124/+240
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Move window geometry calculation to helperJonas Ådahl2016-08-251-7/+21
| | | | | | We'll use it from more places later. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Only update the window title if it actually updatedJonas Ådahl2016-08-251-0/+3
| | | | | | This makes the protocol log less spammy. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Only sync surface regions once per commitJonas Ådahl2016-08-251-8/+25
| | | | | | | | Only set input, opaque and window geometry regions once per commit. They are double buffered anyway, so the last one would only take effect either way; this way reading protocol logs are much more pleasent. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Remove gdk_wayland_display_get_xdg_shell()Jonas Ådahl2016-08-252-20/+0
| | | | | | | Don't expose the xdg_shell struct as it is not yet a stable type that will stay the same. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Get tiled state from gtk_shell instead of xdg_shellJonas Ådahl2016-08-252-11/+52
| | | | | | | Use our the 'tiled' entry from our new 'state' enum sent via xdg_surface.configure. https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Fix indentationJonas Ådahl2016-08-251-13/+13
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=769937
* wayland: Add some more debug spewMatthias Clasen2016-08-251-0/+9
|
* wayland: Replace g_debug by GDK_NOTEMatthias Clasen2016-08-252-53/+81
| | | | We have this framework, lets use it.
* Document window-icon related api as 'may not work'Matthias Clasen2016-08-242-6/+12
| | | | Some platforms simply don't have window icons (such as Wayland).
* notebook: Update arrow state when switching pagesMatthias Clasen2016-08-241-0/+3
| | | | | | | Otherwise, we may end up showing clickable arrows that don't do anything. https://bugzilla.gnome.org/show_bug.cgi?id=770332
* scale: Document interaction between rounding and autoscrollingMatthias Clasen2016-08-241-0/+5
| | | | This is a bit of a gotcha, so better document it.
* widget-factory: Fix smooth autoscrolling of scalesMatthias Clasen2016-08-242-2/+12
| | | | | | | | | There is annoying interference between formatting the value (for which we set the number of digits to show) and the small frame-to-frame value changes that we do for autoscrolling. To work around this, turn off the digits-based rounding entirely and format the value ourselves with ::format-value.
* gtk-demo: Make the scale demo fully functionalMatthias Clasen2016-08-241-0/+6
| | | | | The adjustments need to have step-increment and page-increment set up, or keynav and autoscrolling will not work.
* Allow activating the desktop portal for inhibitMatthias Clasen2016-08-241-1/+1
| | | | We allow it everywhere else, and there is nothing wrong with it.
* Updated Czech translationMarek Černocký2016-08-241-16/+32
|
* Updated Spanish translationDaniel Mustieles2016-08-241-186/+204
|
* Update POTFILES.in and POTFILES.skipPiotr Drąg2016-08-234-0/+4
|
* demos: Use stateful actions for rings/strips in "Touch and Drawing Tablets" demoCarlos Garnacho2016-08-231-6/+31
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=770026
* GtkPadController: Make ring/strip actions be activated with the axis valueCarlos Garnacho2016-08-231-1/+24
| | | | | | This way these axes may be used in detail by the implementors of pad GActions. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* GtkEventController: Add some comment describing the filter_event private vfuncCarlos Garnacho2016-08-231-0/+3
| | | | | | It might not be entirely clear what the boolean return value means. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* demos: Add pad support to "event axes" demoCarlos Garnacho2016-08-231-4/+106
| | | | | | | | | | | And rename it to "Touch and Drawing Tablets", since it's no longer about "axes" really. As for pad support in the demo, just keep it "simple", make the controller handle all pad devices, and make all the actions have the same callback. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* GtkPadController: Notify actions back to the windowing on waylandCarlos Garnacho2016-08-231-0/+30
| | | | | | | This allows applications to provide descriptions of the actions performed by each pad feature. pass the GtkPadActionEntry labels for this. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Offer wayland-specific method to set pad actions feedbackCarlos Garnacho2016-08-232-0/+68
| | | | | | | | The wayland tablet protocol allows notifying the compositor with descriptions of the actions performed by each tablet element. This API call allows to hook up in to this wayland-specific feature. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Support pad devices in gdk_wayland_device_get_node_path()Carlos Garnacho2016-08-231-1/+6
| | | | | | We can return the node path on those too, so do that. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Implement pad event emissionCarlos Garnacho2016-08-231-1/+100
| | | | | | We now send all the set of button/ring/strip/group_mode events. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Create/expose pad devicesCarlos Garnacho2016-08-231-0/+27
| | | | | | | | | These devices are kind of an strange case. Their "master" device is the keyboard, because they share toplevel focus with it, regardless of stylus focus. Nonetheless, they are only expected to send the GdkEventPad* set of events. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Add GdkWaylandDevicePadCarlos Garnacho2016-08-231-0/+166
| | | | | | | | This is a subclass of GdkWaylandDevice that implements GdkDevicePad, all pad features are looked up from the info obtained through the tablet v2 interface. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* wayland: Implement backbone of pad supportCarlos Garnacho2016-08-231-2/+397
| | | | | | | All pad interfaces and features are poked, we just now need exposing those. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* gtk: Add GtkPadControllerCarlos Garnacho2016-08-237-1/+594
| | | | | | | | | | | | | | This GdkEventController is a helper object to handle pad events, it allows setting a mapping to action names, to be triggered in the given action group. In order to help on places where advanced mapping/configurability of pad features is not desirable, this controller also allows passing a NULL pad device, meaning it will listen on all pads, and/or passing -1 on mode/index, so an action applies to all modes/features (eg. strips/rings). https://bugzilla.gnome.org/show_bug.cgi?id=770026
* gtk: Add minimal handling of pad eventsCarlos Garnacho2016-08-232-0/+10
| | | | | | No real handling is yet performed, to be done through a GdkEventController https://bugzilla.gnome.org/show_bug.cgi?id=770026
* gdk: Add GdkDevicePadCarlos Garnacho2016-08-238-0/+294
| | | | | | | | | | | | This is an interface meant to be implemented by the "pad" devices. This device-specific interface exposes the mapping of all pad features, it allows retrieving: - The number of buttons/rings/strips - The number of groups - The number of modes a group has - Whether a given button/ring/strip belongs to a given group https://bugzilla.gnome.org/show_bug.cgi?id=770026
* gdk: Address pad events similarly to keyboard eventsCarlos Garnacho2016-08-231-1/+2
| | | | | | | | | | We want the same treatment for those, the event will be emitted on the toplevel, which will then decide what to do with the event. It just doesn't make much sense to propagate those up/down the hierarchy, when we want specifically one action being triggered from those. https://bugzilla.gnome.org/show_bug.cgi?id=770026
* gdk: Add pad event structs, enum values, and event mask bitCarlos Garnacho2016-08-235-0/+133
| | | | | | | | | | | | | | GDK_PAD_BUTTON*,RING and STRIP will be emitted respectively when pad buttons, rings or strips are interacted with. Each of those pad components belong to a group (a pad can contain several of those), which may be in a given mode. All this information is contained in the event. GDK_PAD_GROUP_MODE is emitted when a group in the pad switches mode, which will generally result in a different set of actions being triggered from the same buttons/rings/strips in the group. https://bugzilla.gnome.org/show_bug.cgi?id=770026
View Lorry Controller Status