- 11 May, 2022 1 commit
-
-
Sophie Herold authored
Those property features don't seem to be in use anywhere. They are redundant since the docs cover the same information and more. They also created unnecessary translation work. Closes #4904
-
- 31 May, 2021 1 commit
-
-
Matthias Clasen authored
GtkBoxLayout stores the orientation; no need for GtkBox to duplicate that.
-
- 21 May, 2021 1 commit
-
-
Matthias Clasen authored
Remove a boatload of "or %NULL" from nullable parameters and return values. gi-docgen generates suitable text from the annotation that we don't need to duplicate. This adds a few missing nullable annotations too.
-
- 11 Mar, 2021 1 commit
-
-
Convert link format, add an example image, add property annotations. General cleanup.
-
- 28 Jan, 2021 1 commit
-
-
Matthias Clasen authored
Remove some unnecessary uses of GtkStyleContext where we can directly go to the GtkCssStyle, and and drop unnnecessary includes.
-
- 03 Jan, 2021 1 commit
-
-
Timm Bäder authored
-
- 21 Dec, 2020 1 commit
-
-
Andrei Lișiță authored
Rephrase a function parameter description and remove "." from all function parameters descriptions Fixes #3499
-
- 12 Nov, 2020 1 commit
-
-
Emmanuele Bassi authored
There are a few widgets that gained an accessible role, which means adding an "Accessibility" section in their description.
-
- 11 Nov, 2020 1 commit
-
-
Emmanuele Bassi authored
Widgets that just provide grouping and layout to other widgets should not be relevant to the accessible tree.
-
- 20 Oct, 2020 1 commit
-
-
Benjamin Otte authored
gtk_widget_insert_after() reorders CSS nodes properly.
-
- 26 Jul, 2020 1 commit
-
-
Emmanuele Bassi authored
To build a better world sometimes means having to tear the old one down. -- Alexander Pierce, "Captain America: The Winter Soldier" ATK served us well for nearly 20 years, but the world has changed, and GTK has changed with it. Now ATK is mostly a hindrance towards improving the accessibility stack: - it maps to a very specific implementation, AT-SPI, which is Linux and Unix specific - it requires implementing the same functionality in three different layers of the stack: AT-SPI, ATK, and GTK - only GTK uses it; every other Linux and Unix toolkit and application talks to AT-SPI directly, including assistive technologies Sadly, we cannot incrementally port GTK to a new accessibility stack; since ATK insulates us entirely from the underlying implementation, we cannot replace it piecemeal. Instead, we're going to remove everything and then incrementally build on a clean slate: - add an "accessible" interface, implemented by GTK objects directly, which describe the accessible role and state changes for every UI element - add an "assistive technology context" to proxy a native accessibility API, and assign it to every widget - implement the AT context depending on the platform For more information, see: #2833
-
- 24 Jul, 2020 2 commits
-
-
Benjamin Otte authored
-
Benjamin Otte authored
-
- 05 Jun, 2020 1 commit
-
-
Emmanuele Bassi authored
It feels slightly wrong to have GtkOrientable operate on widgets, but at least what happens when an orientable widget changes orientation should be part of GtkWidget. This will allow to add more state changes without accessing widget state from the outside of gtkwidget.c.
-
- 12 May, 2020 2 commits
-
-
Matthias Clasen authored
-
Matthias Clasen authored
Add replacement api for gtk_container_add/remove.
-
- 07 Feb, 2020 1 commit
-
-
Just like we do everywhere else. This way we can also get rid of all the prototypes.
-
- 28 Jan, 2020 1 commit
-
-
Benjamin Otte authored
-
- 21 Jan, 2020 1 commit
-
-
Benjamin Otte authored
-
- 09 Sep, 2019 1 commit
-
-
Timm Bäder authored
-
- 28 May, 2019 1 commit
-
-
Matthias Clasen authored
These serve no purpose anymore - widgets don't have surfaces, unless they're a GtkNative.
-
- 06 May, 2019 1 commit
-
-
Emmanuele Bassi authored
Instead of manually creating the layout manager inside the instance initialization function, we can let GtkWidget do that for us.
-
- 26 Mar, 2019 1 commit
-
-
Emmanuele Bassi authored
We can delegate all the layout management to a GtkBoxLayout, now that we have one.
-
- 05 Feb, 2019 1 commit
-
-
Matthias Clasen authored
Not needed anymore.
-
- 24 Jan, 2019 7 commits
-
-
Matthias Clasen authored
Change the reorder api to insert after a sibling, so that moving to first place becomes reorder (... NULL). And add a insert_after api that can replace the common container_add / reorder_after (... NULL) combination. Update all callers.
-
Matthias Clasen authored
The position child property is problematic, since it requires us to emit notification for all children when inserting a child early in the list of children. Remove the property from all ui files.
-
-
-
Remove all references to any sort of "packing".
-
GtkWidget saves a widget list for us, so we don't need to keep track of them ourselves. This is okay now that we don't have a pack-type child property anymore.
-
-
- 04 Dec, 2018 1 commit
-
-
Daniel Boles authored
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.
-
- 13 Nov, 2018 1 commit
-
-
Timm Bäder authored
The values have been 0/0 for a long time now, so just drop the GtkAllocation argument and replace it with width and height.
-
- 27 Aug, 2018 3 commits
-
-
Timm Bäder authored
One function to measure the box in the opposite of its internal direction is enough.
-
Timm Bäder authored
So we call it like we call it everywhere else.
-
Timm Bäder authored
-
- 18 Jun, 2018 1 commit
-
-
Timm Bäder authored
Make :first-child always be the first child, i.e. the leftest one in LTR and the rightest one in RTL.
-
- 05 Apr, 2018 1 commit
-
-
Benjamin Otte authored
As the clip is no longer needed, get rid of it.
-
- 20 Mar, 2018 1 commit
-
-
Alexander Larsson authored
This is an automated change doing these command: git sed -f g gtk_widget_set_has_window gtk_widget_set_has_surface git sed -f g gtk_widget_get_has_window gtk_widget_get_has_surface git sed -f g gtk_widget_set_parent_window gtk_widget_set_parent_surface git sed -f g gtk_widget_get_parent_window gtk_widget_get_parent_surface git sed -f g gtk_widget_set_window gtk_widget_set_surface git sed -f g gtk_widget_get_window gtk_widget_get_surface git sed -f g gtk_widget_register_window gtk_widget_register_surface git sed -f g gtk_widget_unregister_window gtk_widget_unregister_surface git checkout NEWS*
-
- 09 Feb, 2018 1 commit
-
-
Timm Bäder authored
-