AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-12-26 21:51:08 +00:00
Code Issues Projects Releases Wiki Activity

Reword release notes

Browse Source
This commit is contained in:
Matthias Clasen 2016-03-20 21:48:05 -04:00
parent bee669ee66
commit f732fa6883
1 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
README.in
View File

@ -72,48 +72,48 @@ and attach the patch to that bug report.
Patches should be in unified diff form. (The -up option to GNU diff) Patches should be in unified diff form. (The -up option to GNU diff)
Even better are git-formatted patches. (Use git format-patch) Even better are git-formatted patches. (Use git format-patch)
Release notes for 3.20 Release notes for 3.20
====================== ======================
* The way theming works in GTK+ has been reworked pretty fundamentally * The way theming works in GTK+ has been reworked fundamentally, to
in this release, to be able to implement many more CSS features and implement many more CSS features and make themes more expressive.
generally give themes more power. As a result, custom CSS that is As a result, custom CSS that is shipped with applications and third-
shipped with applications and third-party themes will need adjustments. party themes will need adjustments. Widgets now use element names much
Widgets now use element names much more than style classes; type more than style classes; type names are no longer used in style matching.
names are no longer used in style matching. Every widget now documents Every widget now documents the element names it has and the style classes
the element names it has and the style classes it uses. The GTK+ it uses. The GTK+ inspector can also help with finding this information.
inspector can also be helpful in finding this information.
* GTK+ now uses internal subobjects (also known as gadgets) for allocating * GTK+ now uses internal subobjects (also known as gadgets) for allocating
and drawing widget parts. Applications that subclass GTK+ widgets may and drawing widget parts. Applications that subclass GTK+ widgets may see
see warnings if they override size_allocate and don't chain up. The warnings if they override the size_allocate vfunc and don't chain up.
proper way to subclass is to chain up in size_allocate. If you don't The proper way to subclass is to chain up in size_allocate. If you do not
want to do that for some reason, you have to override draw as well. want to do that for some reason, you have to override the draw vfunc as
well.
* Several fixes for window sizing and placement with client-side * Several fixes for window sizing and window placement with client-side
decorations may affect applications that are saving and restoring decorations may affect applications that are saving and restoring window
window sizes. The recommended best practice for this which is known sizes. The recommended best practice for this which is known to work with
to work with client-side and server-side decorations and with older client-side and server-side decorations and with older and newer versions
and newer versions of GTK+ is to use gtk_window_get_size() to save of GTK+ is to use gtk_window_get_size() to save window sizes and
and gtk_window_set_default_size() to restore the window size. See gtk_window_set_default_size() to restore it.
https://wiki.gnome.org/HowDoI/SaveWindowState for a detailed example. See https://wiki.gnome.org/HowDoI/SaveWindowState for a detailed example.
* GtkDrawingArea used to implicitly render the theme background before * GtkDrawingArea used to implicitly render the theme background before
calling the ::draw handler. This is no longer the case. If you rely calling the ::draw handler. This is no longer the case. If you rely
on having a theme-provided background, call gtk_render_background() on having a theme-provided background, call gtk_render_background()
from your ::draw handler. from your ::draw handler.
* The GtkFileChooser interface pre-requisite changed from GtkWidget * The GtkFileChooser interface prerequisite changed from GtkWidget
to GObject, allowing non-widget implementations of this interface. to GObject, allowing non-widget implementations of this interface.
This is a minor change in ABI, as apps are no longer guaranteed This is a minor change in ABI, as applications are no longer guaranteed
that a GtkFileChooser interface also supports all GtkWidget methods. that a GtkFileChooser also supports all GtkWidget methods. However, all
However, all previously existing objects still derive from GtkWidget, previously existing implementations still derive from GtkWidget, so no
so no existing code should break. existing code should break.
* The way in which GtkLevelBar determines the offset to apply was * The way in which GtkLevelBar determines the offset to apply was a bit
a bit inconsistent in the past; this has been fixed. Applications inconsistent in the past; this has been fixed. Applications that are using
that are using custom offsets should double-check that their custom offsets should double-check that their levels look as expected.
levels look as expected.
Release notes for 3.18 Release notes for 3.18
====================== ======================