| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The previous way of manually juggling the visibility of the
labels doesn't work anymore, now that gadgets of invisible
widgets don't allocate space anymore.
|
|
|
|
|
| |
Instead of a separate element name, keep button, and just
add a .lock style class, to inherit the button theming.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=728992
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We rename the gtk_widget_class_bind_template_child{_internal}
macros by appending a _private to their name. Otherwise, it
would be too magic to pass the 'public' names as arguments,
but affect a member of the Private struct. At the same time,
Add two new macros with the old names,
gtk_widget_class_bind_template_child{_internal} that operate
on members of the instance struct.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The macros and functions are inconsistently named, and are not tied to
the "template" concept - to the point that it seems plausible to use
them without setting the template.
The new naming scheme is as follows:
gtk_widget_class_bind_template_child_full
gtk_widget_class_bind_template_callback_full
With the convenience macros:
gtk_widget_class_bind_template_child
gtk_widget_class_bind_template_child_internal
gtk_widget_class_bind_template_callback
https://bugzilla.gnome.org/show_bug.cgi?id=700898
https://bugzilla.gnome.org/show_bug.cgi?id=700896
|
|
|
|
|
|
|
|
|
|
| |
Using an offset from the struct means you can have children in
both the public and private (via G_PRIVATE_OFFSET) parts of the
instance. It also matches the new private macros nicer.
https://bugzilla.gnome.org/show_bug.cgi?id=702563
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit exposes the get_type() functions and standard
headers for accessible implementations. This makes it possible
to derive from the GTK accessible implementations without
GType magic tricks. This is necessary, because we require the
a11y type hierarchy to be parallel to the widget type hierarchy.
So, if you derive a widget and need to adjust its a11y implementation,
you have to be able to derive its accessible implementation.
This commit probably exposes more than is absolutely necessary,
it also exposes accessibles of widgets that are unlikely candidates
for deriving from.
|
|
|
|
|
|
|
| |
In particular, ensure that the name of the lockbutton gets updated as
the displayed text of the lockbutton changes.
https://bugzilla.gnome.org/show_bug.cgi?id=677347
|
|
|
|
|
|
|
| |
Instead of letting the generic button code attempt to find the currently
displayed text, just return the text directly.
https://bugzilla.gnome.org/show_bug.cgi?id=677347
|
|
|
|
|
| |
The accessible doesn't do anything yet, this is just infrastructure
work.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=659613
|
|
|
|
|
| |
Most of these are forgotten :'s and similar details
which gtk-doc now warns about.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=651734
|
|
|
|
|
| |
Now it is actually just a button, which makes things simpler
and is closer to what the designers want.
|
|
|
|
| |
This is useful in some scenarios.
|
|
This is a special-purpose button that can be used together with
GPermission objects to control the sensitivity of system settings.
Suitable permission objects can e.g. be obtained from PolicyKit.
http://bugzilla.gnome.org/show_bug.cgi?id=626457
|