callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mention type vs region ambiguity in the docs

Browse Source
This commit is contained in:
Matthias Clasen 2011-01-19 12:55:48 -05:00
parent d45a0114a5
commit 0a5e8ce685
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
gtk/gtkcssprovider.c
View File

@ -157,6 +157,12 @@
* style classes they define and see <xref linkend="gtkstylecontext-classes"/> * style classes they define and see <xref linkend="gtkstylecontext-classes"/>
* for a list of all style classes used by GTK+ widgets. * for a list of all style classes used by GTK+ widgets.
* </para> * </para>
* <para>
* Note that there is some ambiguity in the selector syntax when it comes
* to differentiation widget class names from regions. GTK+ currently treats
* a string as a widget class name if it contains any uppercase characters
* (which should work for more widgets with names like GtkLabel).
* </para>
* <example> * <example>
* <title>Style classes in selectors</title> * <title>Style classes in selectors</title>
* <programlisting language="text"> * <programlisting language="text">
@ -1718,7 +1724,8 @@ is_widget_class_name (const gchar *str)
* widget class names contain only CamelCase * widget class names contain only CamelCase
* (gtkmm widgets don't), but at least part of * (gtkmm widgets don't), but at least part of
* the name will be CamelCase, so check for * the name will be CamelCase, so check for
* the first uppercase char */ * the first uppercase char
*/
while (*str) while (*str)
{ {
if (g_ascii_isupper (*str)) if (g_ascii_isupper (*str))