*: Fix spelling mistakes found by codespell
This commit is contained in:
@@ -5,7 +5,7 @@ This document is intended to be a short description of the preferred
|
||||
coding style to be used for the GTK source code. It was strongly
|
||||
inspired by Clutter's `CODING_STYLE`.
|
||||
|
||||
Coding style is a matter of consistency, readability and maintainance;
|
||||
Coding style is a matter of consistency, readability and maintenance;
|
||||
coding style is also completely arbitrary and a matter of taste. This
|
||||
document will use examples at the very least to provide authoritative
|
||||
and consistent answers to common questions regarding the coding style,
|
||||
|
||||
@@ -101,7 +101,7 @@ allow use of detailed action names. This is a convenient way of specifying
|
||||
an action name and an action target with a single string.
|
||||
|
||||
In the case that the action target is a string with no unusual characters
|
||||
(ie: only alpha-numeric, plus '-' and '.') then you can use a detailed
|
||||
(ie: only alphanumeric, plus '-' and '.') then you can use a detailed
|
||||
action name of the form "justify::left" to specify the justify action with
|
||||
a target of left.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ name, a state and possibly style classes. The children of each node
|
||||
are linearly ordered.
|
||||
|
||||
Every widget has one or more of these CSS nodes, and determines their
|
||||
name, state, style classes and how they are layed out as children and
|
||||
name, state, style classes and how they are laid out as children and
|
||||
siblings in the overall node tree. The documentation for each widget
|
||||
explains what CSS nodes it has.
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ functions, types and macros required by GTK applications.
|
||||
|
||||
Even if GTK installs multiple header files, only the top-level `gtk/gtk.h`
|
||||
header can be directly included by third-party code. The compiler will abort
|
||||
with an error if any othe header is directly included.
|
||||
with an error if any other header is directly included.
|
||||
|
||||
In a GTK application, the purpose of the main() function is to create a
|
||||
GtkApplication object and run it. In this example a GtkApplication pointer
|
||||
@@ -205,7 +205,7 @@ variable is created to store a GtkBox, which is GTK's way of controlling
|
||||
the size and layout of buttons.
|
||||
|
||||
The GtkBox is created with gtk_box_new() which takes a GtkOrientation
|
||||
enum as parameter. The buttons which this box will contain can either be layed
|
||||
enum as parameter. The buttons which this box will contain can either be laid
|
||||
out horizontally or vertically. This does not matter in this particular case,
|
||||
as we are dealing with only one button. After initializing box with the newly
|
||||
created GtkBox, the code adds the box widget to the window widget using
|
||||
|
||||
@@ -70,7 +70,7 @@
|
||||
<term>--force</term>
|
||||
<term>-f</term>
|
||||
<listitem><para>Overwrite an existing cache file even if it appears to be
|
||||
uptodate.</para></listitem>
|
||||
up-to-date.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
|
||||
@@ -128,7 +128,7 @@ Mnmemonics
|
||||
They are used in places where a label is associated with a control,
|
||||
and are indicated by underlining the letter in the label. As a special
|
||||
case, inside menus (i.e. inside #GtkPopoverMenu), mnemonics can be
|
||||
trigered without the modifier.
|
||||
triggered without the modifier.
|
||||
Key bindings
|
||||
: Key bindings are specific to individual widgets, such as Ctrl-C or
|
||||
Ctrl-V in an entry copy to or paste from the clipboard. They are only
|
||||
|
||||
@@ -533,7 +533,7 @@ adding children with <child> in ui files.
|
||||
The abstract base class GtkContainer for general containers has been
|
||||
removed. The former subclasses are now derived directly from GtkWidget,
|
||||
and have class-specific add() and remove() functions.
|
||||
The most noticable change is the use of gtk_box_append() or gtk_box_prepend()
|
||||
The most noticeable change is the use of gtk_box_append() or gtk_box_prepend()
|
||||
instead of gtk_container_add() for adding children to GtkBox, and the change
|
||||
to use container-specific remove functions, such as gtk_stack_remove() instead
|
||||
of gtk_container_remove(). Adding a child in a ui file with <child> still works.
|
||||
@@ -671,7 +671,7 @@ gradients, just use those.
|
||||
|
||||
GTK now supports a more versatile -gtk-icon-filter instead. Replace
|
||||
-gtk-icon-effect: dim; with -gtk-icon-filter: opacity(0.5); and
|
||||
-gtk-icon-effect: hilight; with -gtk-icon-filter: brightness(1.2);.
|
||||
-gtk-icon-effect: highlight; with -gtk-icon-filter: brightness(1.2);.
|
||||
|
||||
### Don't use -gtk-icon-theme in your CSS
|
||||
|
||||
@@ -701,7 +701,7 @@ of connecting a handler to the #GtkWidget::draw signal.
|
||||
### Stop using APIs to query GdkSurfaces
|
||||
|
||||
A number of APIs for querying special-purpose windows have been removed,
|
||||
since these windows are no longer publically available:
|
||||
since these windows are no longer publicly available:
|
||||
gtk_tree_view_get_bin_window(), gtk_viewport_get_bin_window(),
|
||||
gtk_viewport_get_view_window().
|
||||
|
||||
|
||||
@@ -445,7 +445,7 @@ the question you have, this list is a good place to start.
|
||||
gtk_list_store_set() and gtk_tree_store_set(), but can't read it back?
|
||||
|
||||
Both the #GtkTreeStore and the #GtkListStore implement the #GtkTreeModel
|
||||
interface. Consequentially, you can use any function this interface
|
||||
interface. Consequently, you can use any function this interface
|
||||
implements. The easiest way to read a set of data back is to use
|
||||
gtk_tree_model_get().
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ Each role name is part of the #GtkAccessibleRole enumeration.
|
||||
| `METER` | Represents a value within a known range | #GtkLevelBar |
|
||||
| `PROGRESS_BAR` | An element that display progress | #GtkProgressBar |
|
||||
| `RADIO` | A checkable input in a group of radio roles | #GtkRadioButton |
|
||||
| `SCROLLBAR` | A graphical object controlling the scolling of content | #GtkScrollbar |
|
||||
| `SCROLLBAR` | A graphical object controlling the scrolling of content | #GtkScrollbar |
|
||||
| `SEARCH_BOX` | A text box for entering search criteria | #GtkSearchEntry |
|
||||
| `SEPARATOR` | A divider that separates sections of content or groups of items | #GtkSeparator |
|
||||
| `SPIN_BUTTON` | A range control that allows seelcting among discrete choices | #GtkSpinButton |
|
||||
|
||||
@@ -128,7 +128,7 @@ GtkWidget *tree;
|
||||
tree = gtk_tree_view_new_with_model (GTK_TREE_MODEL (store));
|
||||
```
|
||||
|
||||
## Colums and cell renderers
|
||||
## Columns and cell renderers
|
||||
|
||||
Once the #GtkTreeView widget has a model, it will need to know how
|
||||
to display the model. It does this with columns and cell renderers.
|
||||
|
||||
Reference in New Issue
Block a user