summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* main: Use the new widget depth when delivering eventswip/baedert/some-apiTimm Bäder2018-12-251-9/+26
|
* window: Don't allocate GLists when changing cursorsTimm Bäder2018-12-251-7/+13
| | | | | We do this all the time when moving the cursor and we can now do it without the GList allocations.
* widget: Save the depth of a widget in the treeTimm Bäder2018-12-252-0/+26
| | | | | This is handy whenever we do some operation on all parent widgets of a widget.
* stack: Don't queue an unnecessary redrawTimm Bäder2018-12-231-2/+2
| | | | Both queue_allocate and queue_resize already queue a draw.
* picture: Avoid some unnecessary signal connectionsTimm Bäder2018-12-221-14/+24
| | | | | We don't need to ever invalidate the picture size if the paintable tells us its size is static. Same for the contents.
* image: Remove private struct from public headerTimm Bäder2018-12-212-3/+2
|
* image: Remove some outdated commentsTimm Bäder2018-12-211-2/+2
|
* mediastream: Fix possible memory leakMohammed Sadiq2018-12-201-1/+4
| | | | @error is (transfer full). So the error passed should be freed if not used
* x11: make the tool lookup dependent on the hw id as wellPeter Hutterer2018-12-184-9/+12
| | | | | | | | | Tools on the same physical item have the same serial number, so the eraser and the pen part of a single pen share that serial number. With the current lookup code, we'll always return whichever tool comes first into proximity. Change the code to use the hw id in addition to the serial number, this way we can differ between two tools.
* x11: don't add unknown tools to our listPeter Hutterer2018-12-181-2/+5
| | | | | | | | | | | | | | | Generic tools (Bamboo, built-in tablets) always have the same serial number assigned by the wacom driver. This includes the touch tool when the wacom driver handles the touch evdev node (common where users require the wacom gestures to work). When the first device is the touch device, a tool is created with that serial. All future tools now return the touch tool on lookup since they all share the same serial number. Worse, this happens *across* devices, so the pen event node gets assigned the touch tool because they all have the same serial. Since we don't actually care about the touch as a tool, let's skip any unknown tool. This captures pads as well.
* x11: get the tool type from the wacom driver propertiesPeter Hutterer2018-12-181-2/+81
| | | | | | | Any wacom device currently sets the tool type to UNKNOWN. The wacom driver has a property that exports the tool type as one of stylus, eraser, cursor, pad or touch. Only three of those are useful here but that's better than having all of them as unknown.
* gstmedia: Implement error handling.Benjamin Otte2018-12-181-0/+14
| | | | | I wonder who forgot that. Whoops.
* mediastream: Allow multiple calls to gtk_media_stream_error()Benjamin Otte2018-12-181-1/+7
| | | | Just ignore all further ones.
* a11y: Fix function return typeBenjamin Otte2018-12-181-1/+1
| | | | Typo right there.
* RGBA: tiny grammar improvements in to_string docDaniel Boles2018-12-171-2/+2
|
* RGBA: Consistently use “” around inline arg namesDaniel Boles2018-12-171-4/+4
| | | | | instead of being inconsistent and not using them later, which leaves a bunch of single letters floating among real words, not the prettiest.
* RGBA: Fix example to_string output for reality/CSSDaniel Boles2018-12-171-2/+2
| | | | | | * We don't output spaces anywhere in the code, unlike the doc suggested. * CSS explicitly forbids whitespace between function names and lparens: https://stackoverflow.com/questions/13877198
* ci: Update Docker image to Fedora 29 and meson to 0.49.0Christoph Reiter2018-12-163-5/+5
|
* Replace git.gnome.org by Gitlab URL in <GitRepository> in DOAP fileAndre Klapper2018-12-161-2/+2
|
* Replace Bugzilla by Gitlab URL in DOAP fileAndre Klapper2018-12-151-1/+1
|
* Remove gtk_widget_show_all() callEmmanuele Bassi2018-12-141-2/+0
| | | | | | Extraneous chunk from 7601bca7587dd29bde3d1554e644a10ae6dafc18. Cherry picked from gtk-3-24, which has a gtk_widget_show_all() function.
* Merge branch 'master' into 'master'Matthias Clasen2018-12-146-1/+326
|\ | | | | | | | | A11y: Add support for AtkTableCell See merge request GNOME/gtk!411
| * A11y: Add support for AtkTableCellMike Gorse2018-12-146-1/+326
|/
* placesview: List only available protocols as availableAntónio Fernandes2018-12-142-121/+53
| | | | | | | | | | | We display a list of supported protocols in the server_addresses_popover. However, this curated list contains protocols which may or may not be available, depending on the respective gvfs backend being installed. So, populate the list only with protocols which are available. https://gitlab.gnome.org/GNOME/gtk/issues/1476
* placesview: Set .error style if unsupported protocolAntónio Fernandes2018-12-141-0/+7
| | | | | | | | | | | | | When the user types an address with a schema that is not supported, the Connect button doesn't become sensitive, but there is no visible feedback at all. This feels unresponsive and leaves the user clueless. While it doesn't help explain why the address doesn't work, this will provide a hint that the input was acknowledged but doesn't work. https://gitlab.gnome.org/GNOME/gtk/issues/1476
* Merge branch 'fix-polygon-svg-recolor' into 'master'Matthias Clasen2018-12-141-1/+1
|\ | | | | | | | | icontheme: Recolor <polygon> elements in SVGs too See merge request GNOME/gtk!443
| * icontheme: Recolor <polygon> elements in SVGs tooPhilip Chimento2018-12-081-1/+1
| | | | | | | | Otherwise, it's possible to have a symbolic icon where some of the shapes keep the #bebebe chroma key color.
* | Merge branch 'demo-combobox-typo-gtk4' into 'master'Timm Bäder2018-12-131-2/+2
|\ \ | | | | | | | | | | | | demos/gtk-demo/combobox: fix typo See merge request GNOME/gtk!444
| * | demos/gtk-demo/combobox: fix typoJeremy Bicha2018-12-091-2/+2
| | | | | | | | | | | | Fix typo that prevented the P-S submenu from displaying correctly
* | | Merge branch 'win32-honest-clipboard-gtk4' into 'master'LRN2018-12-111-44/+8
|\ \ \ | | | | | | | | | | | | | | | | GDK W32: Be honest about supported clipboard formats (GTK4) See merge request GNOME/gtk!399
| * | | GDK W32: Be honest about supported clipboard formatsРуслан Ижбулатов2018-10-311-44/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not lie to W32 about the formats that we provide or accept. Originally the logic behind such lies was that GdkPixbuf allows us to convert any supported image to BMP or PNG, and therefore we should announce that we always provide/accept BMP and PNG along with other formats. But that's not how it works. GDK has built-in serializers and deserializers for all pixbuf formats (where it just invokes GdkPixbuf API) and will use them automatically to read or write GdkTexture objects (internally wrapping GdkPixbuf objects where necessary). The encoding and decoding of images is handled by GdkContent(De)Serializers, backend has nothing to do with it. Therefore W32 GDK backend should only offer formats that it can actually do conversion for by itself (such as image/bmp <-> CF_DIB, or text/uri-list <-> CFSTR_SHELLIDLIST).
* | | | Revert "Adwaita: GNOME 3.32"Jakub Steiner2018-12-105-401/+323
| | | | | | | | | | | | | | | | This reverts all GNOME 3.32 styling from master
* | | | GDK W32: Always set gtk-font-name to the active UI font. Fixes #1484Christoph Reiter2018-12-102-49/+46
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes apps use "Segoe UI 9" by default instead of whatever matches "Sans 10". It also cleans up the code and uses some new pango API while at it. This was previously disabled in 9e686d1fb5cb20 because it led to a poor glyph coverage on certain versions of Windows which don't default to "Segoe UI 9" (Chinese, Korean, ..) because the font fallback list was missing in pango. This is about to get fixed in https://gitlab.gnome.org/GNOME/pango/merge_requests/34 so enable it again when we detect a new enough pango version. (See !436 for the original MR)
* | | Updated Slovenian translationMatej Urbančič2018-12-091-368/+487
| | |
* | | win32: Don't multiply the scroll event deltas by the Windows scroll lines ↵Christoph Reiter2018-12-081-14/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | setting. See #1408 GTK widgets expect the scroll deltas to be 1 or -1 and calculate a scroll value from that. Multiplying the delta by the Windows scroll line setting (which defaults to 3) results in a much larger delta and vastly different behaviour for running a GTK app on Windows vs on Linux. For example text view and tree view scroll by 9 lines per scroll wheel tick per default this way while on Linux it is around 3. Remove the multiplication for now. See !426 for the gtk3 MR
* | | GDK W32: set default settings for fontconfig.Christoph Reiter2018-12-081-0/+36
| |/ |/| | | | | | | | | | | | | Enables hinting, antialiasing and set the subpixel orientation according to the active clear type setting. This ensures that font rendering with the fontconfig backend looks similar to the win32 backend, at least with the default system font. See !437
* | menushell: Listen to non-primary button clicksTimm Bäder2018-12-071-0/+1
| | | | | | | | Menus should also be deactivated on right-button clicks.
* | gl renderer: Track border width state separatelyTimm Bäder2018-12-073-18/+45
| |
* | gl renderer: Ignore subsequent render target opsTimm Bäder2018-12-071-3/+22
| |
* | gl renderer: Ignore viewport ops to the same viewportTimm Bäder2018-12-071-2/+13
| |
* | gesturestylus: Use proper syntax when refering to signalsTimm Bäder2018-12-071-4/+4
| |
* | Adwaita: regenerate CSSJakub Steiner2018-12-072-8/+20
| | | | | | | | - for the previous patch
* | Merge branch 'context_menus' into 'master'Jakub Steiner2018-12-071-4/+17
|\ \ | | | | | | | | | | | | Adwaita GTK Theme: Add bigger shadow and border-radius to menus See merge request GNOME/gtk!432
| * | Adapt border-radius and box-shadow of menus to popoversfrederik.feichtmeier2018-11-301-3/+3
| | |
| * | Add bigger shadow and border-radius to menusfrederik.feichtmeier2018-11-281-3/+16
| | | | | | | | | | | | | | | | | | Increase the visibility of the box-shadow for menus Introduce a border-radius variable for menus Use this variable for all corners of menus except top for the top menus
* | | Adwaita: buttons & headerbar tweaksJakub Steiner2018-12-053-48/+48
| | | | | | | | | | | | | | | - tone down the button z-depth - flatter headerbars
* | | Box, Grid: Improve various bits of documentationDaniel Boles2018-12-042-16/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #1495 showed that the docs of GtkGrid retain outdated implications that (as was once, but is no longer, the case) it is intended to replace GtkBox, by discussing HfW and widget properties in a way that suggests GtkBox can't handle them. But of course it does, and it's preferable for simple single-row/column cases. Worse, we said GtkGrid “provides exactly the same functionality” for the latter case, but the original point of that Issues was that it doesn’t, at least for CSS positional selectors! Box: • Use an actually meaningful @Short_description. • Remove unhelpful @See_also references to unrelated containers. • Remove references to “rectangular area”: it might be another shape via CSS, or “rectangular” might falsely imply 2 dimensions of children. • Mention Orientable:orientation. • Emphasise usefulness of :[hv]align for allocating in the other axis. • Don’t say that Grid “provides exactly the same functionality” for a single row or column, since (A) it is overkill for that case and (B) said Issue proved that it *doesn’t* for CSS child order, for example. Grid: • Don’t dwell on widget properties and height-for-width in a way that wrongly implies that Box can’t handle those (or Grid can better). In fact, just get rid of that bit altogether: Box handles them fine, and such wording was only needed years ago for migration from GTK+ 2 to 3. • Point to GtkBox as being preferred for the simple row/column use case.
* | | Merge branch 'bye-app-menu-gtk4' into 'master'Timm Bäder2018-12-043-22/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | widget-factory: move app menu contents to primary menu (gtk4) Closes #916 See merge request GNOME/gtk!365
| * | | widget-factory: Add Keyboard Shortcuts menu itemJeremy Bicha2018-09-301-0/+4
| | | | | | | | | | | | | | | | Closes: https://gitlab.gnome.org/GNOME/gtk/issues/916
| * | | widget-factory: Rename About menu item to About Widget FactoryJeremy Bicha2018-09-301-1/+1
| | | | | | | | | | | | | | | | | | | | This follows the recommendation in https://gitlab.gnome.org/GNOME/Initiatives/wikis/App-Menu-Retirement
View Lorry Controller Status