Lerking/gtk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Remove mentions of <accelerator>

Browse Source 
That is no longer supported, keyboard shortcuts
are done with GtkShortcut now.

Fixes: #3429
This commit is contained in:
Matthias Clasen
2020-12-02 19:59:44 -05:00
parent 714c610d6b
commit ab9e99218f
2 changed files with 4 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
gtk/gtkbuildable.h
View File

@@ -110,8 +110,8 @@ struct _GtkBuildableParser
* @custom_tag_start: Implement this if the buildable needs to parse
* content below <child>. To handle an element, the implementation
* must fill in the @parser and @user_data and return %TRUE.
* #GtkWidget implements this to parse keyboard accelerators specified
* in <accelerator> elements.
* #GtkWidget implements this to parse accessible attributes specified
* in <accessibility> elements.
* Note that @user_data must be freed in @custom_tag_end or @custom_finished.
* @custom_tag_end: Called for the end tag of each custom element that is
* handled by the buildable (see @custom_tag_start).

11
gtk/gtkwidget.c
View File

@@ -249,15 +249,8 @@
* # GtkWidget as GtkBuildable
*
* The GtkWidget implementation of the #GtkBuildable interface supports a
* custom `<accelerator>` element, which has attributes named ”key”, ”modifiers”
* and ”signal” and allows to specify accelerators.
*
* An example of a UI definition fragment specifying an accelerator:
* |[
* <object class="GtkButton">
* <accelerator key="q" modifiers="GDK_CONTROL_MASK" signal="clicked"/>
* </object>
* ]|
* custom elements to specify various aspects of widgets that are not
* directly expressed as properties.
*
* If the parent widget uses a #GtkLayoutManager, #GtkWidget supports a
* custom `<layout>` element, used to define layout properties: