| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Connect properties, getters, and setters with annotations.
|
|
|
|
| |
Connect properties, getters, and setters with annotations.
|
|
|
|
| |
Change link syntax, add an example image, generally clean things up.
|
|
|
|
| |
Change link syntax, add an example image, generally clean things up.
|
| |
|
|
|
|
|
| |
GtkBindingSignal does not exist anymore, so link to
GtkSignalAction for an explanation of keybinding signals.
|
| |
|
| |
|
|
|
|
|
|
| |
Replace most remaining uses of GTK+ in the docs and
user-visible strings by GTK. Also remove some leftover
"Was added in 3.x" sentences from the docs.
|
|
|
|
|
|
| |
We document the supported style classes by name,
not by macro name, and these macros don't really
add any value. Drop them for GTK 4.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: https://gitlab.gnome.org/GNOME/gtk/-/issues/2833
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
These are all on GtkBox or enumerating children.
|
|
|
|
| |
GtkContainer is going away.
|
|
|
|
| |
This is a replacement for container api that is going away.
|
|
|
|
|
| |
This is mainly for completeness, since gtk_container_remove
will not work for those anymore.
|
|
|
|
|
| |
Replace all uses of gtk_container_add on revealers
with gtk_revealer_set_child.
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit 3ac4c76b18cc89a841ce09f0943539f16988fd21, reversing
changes made to 6ec96d2e989d029a303b8b20ec72b86f974c0e87.
|
| |
|
|
|
|
|
|
| |
Accessors like these are weird to have and we can add widgets to the
content area via gtk_container_add() as well as add widgets to the
action area via gtk_info_bar_add_action_widget().
|
|
|
|
|
| |
We can already set and query that value via
gtk_widget_{get,set}_visible() on the close button.
|
|
|
|
| |
We want to use css instead of style everywhere now.
|
| |
|
|
|
|
| |
As a container, that is what you have to do.
|
|
|
|
|
|
|
| |
When we have a default action set on the infobar, activate it
for clicks anywhere in the infobar. Also add an .action style
class in this case, so we can add a hover highlight to the infobar
just for this case.
|
| |
|
|
|
|
|
|
|
| |
infobars being a GtkBox doesn't make sense.
Also implement infobars without exposing internal children.
Closes #1957 because it adds the bottom border.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Similar to previous removals of g_cclosure_marshal_VOID__VOID we can remove
other marshallers for which are a simple G_TYPE_NONE with single parameter.
In those cases, GLib will setup both a c_marshaller and va_marshaller for
us. Before this commit, we would not get a va_marshaller because the
c_marshaller is set.
Related to GNOME/Initiatives#10
|
|
|
|
|
|
|
| |
If we set c_marshaller manually, then g_signal_newv() will not setup a
va_marshaller for us. However, if we provide c_marshaller as NULL, it will
setup both the c_marshaller (to g_cclosure_marshal_VOID__VOID) and
va_marshaller (to g_cclosure_marshal_VOID__VOIDv) for us.
|
| |
|
|
|
|
|
|
| |
It was added at a time when default buttons
had a very large external border that would disrupt
aligment. Not a problem nowadays.
|
|
|
|
| |
Replace gtk_widget_grab_default by gtk_window_set_default_widget.
|
|
|
|
| |
And make sure it's included everywhere it's needed.
|
|
|
|
|
| |
Additions and correction all over the place,
in GDK and GTK docs.
|
| |
|
|
|
|
|
| |
This widget does not seem worth keeping,
and we want to get rid of child properties.
|
|
|
|
| |
It might soon go away!
|
| |
|
|
|
|
|
|
|
| |
Remove all the old 2.x and 3.x version annotations.
GTK+ 4 is a new start, and from the perspective of a
GTK+ 4 developer all these APIs have been around since
the beginning.
|
| |
|
|
|
|
| |
This avoids a bunch of strdups at startup.
|
|
|
|
|
|
| |
We don't use the gtk_render apis internally anymore.
Drop these includes so it is clear where the remaining
uses are.
|
|
|
|
|
|
| |
mostly: syncing with previous commit, where InfoBar copied this all from
Also, remove my unhelpful “and vice-versa” from InfoBar.
|