summaryrefslogtreecommitdiff
path: root/gtk/gtklockbutton.c
Commit message (Collapse)AuthorAgeFilesLines
* Another round of template binding api changesMatthias Clasen2013-07-261-5/+5
| | | | | | | | | | | 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.
* Rename the widget template APIEmmanuele Bassi2013-07-261-5/+5
| | | | | | | | | | | | | | | | | | | | 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
* widget: Use a real offset in gtk_widget_class_automate_childAlexander Larsson2013-07-261-5/+5
| | | | | | | | | | 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>
* gtk: Use new macros for defining private dataEmmanuele Bassi2013-07-091-6/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702996
* GtkLockButton: Define children with a GtkBuilder templateTristan Van Berkom2013-04-081-21/+10
|
* Make accessible implementations publicMatthias Clasen2012-12-271-1/+1
| | | | | | | | | | | | | | 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.
* a11y: Make lockbutton notify about state changesBenjamin Otte2012-07-091-2/+8
| | | | | | | 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
* a11y: Get lockbutton text directlyBenjamin Otte2012-07-091-1/+17
| | | | | | | 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
* a11y: Add separate accessible for GtkLockButtonBenjamin Otte2012-07-091-0/+4
| | | | | The accessible doesn't do anything yet, this is just infrastructure work.
* Reword lockbutton docsMatthias Clasen2012-05-261-10/+10
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=659613
* Fix malformed doc commentsMatthias Clasen2012-04-121-1/+1
| | | | | Most of these are forgotten :'s and similar details which gtk-doc now warns about.
* Change FSF AddressJavier Jardón2012-02-271-3/+1
|
* lockbutton: ensure the lock symbolic icon is rendered 16x16pxCosimo Cecchi2011-06-061-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=651734
* Simplify GtkLockButtonMatthias Clasen2011-05-251-214/+75
| | | | | Now it is actually just a button, which makes things simpler and is closer to what the designers want.
* Allow NULL permissionsMatthias Clasen2011-05-211-2/+2
| | | | This is useful in some scenarios.
* Add a lock button widgetMatthias Clasen2011-05-061-0/+703
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