Benjamin Otte
541926089a
notebook: Set prelight state properly
...
Don't update it on save/restore, actually set it when it changes.
2015-10-22 16:42:47 +02:00
Benjamin Otte
3392d53f61
notebook: Use CssNodes instead of regions
...
This almost makes CSS work again with notebooks.
2015-10-22 16:42:47 +02:00
Benjamin Otte
01f7711307
notebook: Move style_context_save() into function
...
This is for future changes.
2015-10-22 16:42:47 +02:00
Benjamin Otte
601fe8f502
css: Remove macros that were used only with regions
2015-10-22 16:42:47 +02:00
Benjamin Otte
55d496e917
cssmatcher: Remove matching API for regions
2015-10-22 16:42:47 +02:00
Benjamin Otte
983de6f4a0
treeview: Use a cssnode instead of regions
...
This makes Treeview headers work again like before region support was
removed.
2015-10-22 16:42:47 +02:00
Benjamin Otte
24dde6346a
API: cssselector: Stop supporting regions
...
The namespace that belonged to regions is supposed to be used for
CssNode names.
2015-10-22 16:42:46 +02:00
Benjamin Otte
20ce0588b1
treeviewcolumn: Create button on init
...
This way, the button is always available and the code doesn't have to
special case this condition.
2015-10-22 16:42:46 +02:00
Benjamin Otte
950b1fb65c
switch: Port to GtkCssNode
...
This is a simple port, no code modifications so far other than replacing
gtk_style_context_save() with gtk_style_context_save_to_node().
2015-10-22 16:42:46 +02:00
Benjamin Otte
c075c14bf4
stylecontext: Add gtk_style_context_save_to_node()
...
To be used instead of gtk_style_context_save() with persistent nodes.
2015-10-22 16:35:14 +02:00
Benjamin Otte
72615a1b16
stylecontext: Add gtk_style_context_add_named()
...
This is an intermediate step for cssnode introduction. It gives a name
for the node created by saving the style context.
2015-10-22 16:35:14 +02:00
Benjamin Otte
385fda80b4
cssmatcher: Marshal name to matcher
...
... and use it in the node matcher.
Also rename function from _gtk_css_matcher_get_type() to
_gtk_css_matcher_get_name().
2015-10-22 16:35:14 +02:00
Benjamin Otte
efff9c8edb
cssnode: Add setters/getters for name
2015-10-22 16:35:14 +02:00
Benjamin Otte
26450a661e
cssnodedeclaration: Add possibility to set the name
...
This is supposed to be a replacement for setting the type. So far, both
options are possible - either will unset the other.
2015-10-22 16:35:14 +02:00
Benjamin Otte
b65f400d56
treeview: Remove "row" and "col" regions
...
They aren't used by the theme and we want to get rid of regions.
2015-10-22 16:35:13 +02:00
Piotr Drąg
92a136ffde
Updated POTFILES.in and POTFILES.skip
2015-10-22 02:01:05 +02:00
Matthias Clasen
1a2cdad220
Update NEWS to mention help overlays
2015-10-21 17:15:17 -04:00
Matthias Clasen
a2e581d54c
Update POTFILES.in
2015-10-21 15:48:20 -04:00
Matthias Clasen
3306ce6819
widget-factory: Add an automatic help overlay
...
This commit add some more keyboard shortcuts to gtk3-widget-factory,
and adds a help overlay documenting them. This examle uses the
automatic resource loading support in GtkApplication.
2015-10-21 15:33:22 -04:00
Matthias Clasen
f6d9f9f93d
Add automatic help overlay support to GtkApplication
...
When the $(resource_prefix)/gtk/help-overlay.ui resource exists,
load a GtkShortcutsWindow from it for each GtkApplicationWindow,
and set up a win.show-help-overlay action with accels <Primary>F1
and <Primary>? to show it.
2015-10-21 15:33:09 -04:00
Matthias Clasen
310781ecdd
gtk-demo: Add a GtkShortcutsWindow demo
...
This example implements the mockups from the help overlay design,
showing off the various features of GtkShortcutsWindow.
2015-10-21 15:32:33 -04:00
Matthias Clasen
d1c81446d7
Add some styling for GtkShortcutsWindow
...
Add some keycap frame around keysyms, and make the stack switcher
buttons rounds. This is very provisional.
2015-10-21 15:32:33 -04:00
Matthias Clasen
1dfbae1aa4
Add GtkShortcutsWindow
...
This is a toplevel window that is tailored towards showing
help for shortcuts in an application. The implementation closely
follows this design: https://wiki.gnome.org/Design/OS/HelpOverlay
This implementation is inspired by earlier work in gnome-builder,
thanks to Christian Hergert.
https://bugzilla.gnome.org/show_bug.cgi?id=756428
2015-10-21 15:19:34 -04:00
Matthias Clasen
f254a4b67f
builder: Support creating GFile objects
...
This is useful, e.g. when creating GFileIcon objects.
2015-10-21 13:42:15 -04:00
Matthias Clasen
e9aa33527f
Don't use g_slist_next in the testsuite
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
2dc63dad34
Don't use g_slist_next in gtktreeview.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
05717fe2df
Don't use g_slist_next in gtktreemodel.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
95c7a539bf
Don't use g_slist_next in gtktextview.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
55bd936b73
Don't use g_slist_next in gtktextlayout.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
b65668a251
Don't use g_slist_next in gtktextdisplay.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
060948d806
Don't use g_slist_next in gtktextchild.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
5dd78f74e0
Don't use g_slist_next in gtktextbufferrichtext.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
50c269f846
Don't use g_slist_next in gtktextbuffer.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
a863b06576
Don't use g_slist_next in gtkstock.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
9727a4c4bf
Don't use g_slist_next in gtkiconfactory.c
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
4d59233ba9
Don't use g_slist_next in the x11 backend
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
364d1a574b
Don't use g_slist_next in the windows backend
...
We generally use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
ffa98cbfa5
Don't use g_slist_next in gdk
...
We generally just use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
ecf5c5ff6e
Don't use g_list_next in gtk3-demo
...
We generally just use ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
b5d3bebae3
Don't use g_list_next in gtkselection.c
...
We generally access ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
ea91670c11
Don't use g_list_next in gtkmain.c
...
We generally access ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
8422633311
Don't use g_list_next in gtkdialog.c
...
We generall access ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
b84797a2c6
Don't use g_list_next in gtkcontainer.c
...
We generally access ->next directory.
2015-10-20 06:14:57 -04:00
Matthias Clasen
a0379d5424
Don't use g_slist_next in gtktextbtree.c
...
We generally access ->next directly.
2015-10-20 06:14:57 -04:00
Matthias Clasen
d0e30994d0
builder: Don't use g_slist_next
...
We just use direct access to list->next all over the place.
2015-10-20 06:14:57 -04:00
Matthias Clasen
45fa145034
builder: Cosmetic changes
...
Use an iter instead of g_hash_table_forall.
2015-10-20 06:14:57 -04:00
Matthias Clasen
eec75ee9d6
Cosmetic changes
...
Line up struct-filling code with the order in the declaration.
2015-10-20 06:14:57 -04:00
Matthias Clasen
65aa367029
Add some more builder parser tests
...
These tests contain non-canonical and non-existing property names.
2015-10-20 06:14:57 -04:00
Matthias Clasen
019078364e
builder: Avoid some unnecessary overhead
...
Only get the class once per object, not once per property.
And don't canonicalize the property name, g_object_class_find_property
does that already.
2015-10-20 06:14:57 -04:00
Inaki Larranaga Murgoitio
eb0b096963
Updated Basque language
2015-10-20 10:50:10 +02:00