| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
The gtk_settings_set_...property functions don't really add
anything over g_object_set(), and we never documented them.
|
|
|
|
|
|
| |
Just recommend g_object_set to override settings. The
gtk_settings_set_..._property functions don't really add
any value.
|
|
|
|
|
|
|
|
|
|
|
|
| |
These match the GSettings that mutter/metacity/gnome-shell have
for this. We change the default for the middle-click action to
none, since lower is just a terrible default.
We're slightly bending the rules here, since we're adding new
settings after .0, but a) it is just barely after .0, and b) settings
are not really application API.
https://bugzilla.gnome.org/show_bug.cgi?id=729782
|
|
|
|
|
|
|
|
| |
Settings have a little more metadata than plain properties. They
can come from different sources. Make this information available
so we can show it in the inspector.
https://bugzilla.gnome.org/show_bug.cgi?id=736971
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=734735
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gdk_x11_display_set_window_scale() affects the interpretation of the
Xft/DPI XSETTING - it is substituted inside GDK with the value of
Gdk/UnscaledDPI xsetting. However, this change is not propagated to
GTK+ and from GTK+ back to gdk_screen_set_resolution() until the
main loop is run.
Fix this by handling the screen resolution directly in gdk/x11.
This requires duplication of code between GDK and GTK+ since we still
have to handle DPI in GTK+ in the case that GdkSettings:gtk-xft-dpi
is set by the application.
https://bugzilla.gnome.org/show_bug.cgi?id=733076
|
|
|
|
|
| |
This ensures that we have a polished out-of-the-box appearance
on all platforms.
|
|
|
|
|
| |
We're using this name in two places, so match what we are doing
for the default theme name, and use a macro.
|
|
|
|
|
|
|
|
|
|
| |
We decided in f8412eca34be6e2e655ad3e09bd97fa2bdcbdae0 that
we still need to react to these for a11y reasons, but left
the (then) harmless property deprecation in place. Now, the
deprecation causes runtime warnings for merely reading the
property, so drop it.
https://bugzilla.gnome.org/show_bug.cgi?id=732667
|
|
|
|
|
| |
Change the default value of the gtk-decoration-layout setting
to menu:minimize,maximize,close. The masses want it that way.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=730745
|
|
|
|
|
|
| |
The icontheme lookup code has a special-case that prefers builtin icons
if the theme name is "hicolor". This is problematic for our reftests,
which run in a barebones environment with not settings.
|
|
|
|
|
| |
This setting determines the duration of a button/touch press to
be considered a long press.
|
|
|
|
|
| |
It has been replaced by GdkRGBA. Time to make it official.
http://bugzilla.gnome.org/show_bug.cgi?id=636695
|
|
|
|
| |
scrolledwindow part 2
|
|
|
|
|
|
|
| |
The initialization is really suboptimal here. This fix at least
makes it so that we don't forget to load modules.
https://bugzilla.gnome.org/show_bug.cgi?id=730306
|
| |
|
|
|
|
|
|
|
|
| |
commit 7f6a964c47ad2f9dcf6a00044d938840ce8f01f2 replaced entities, but
escaped the replacement text also inside literals, which resulted in the
escaping '\' to also appear in the documentation.
https://bugzilla.gnome.org/show_bug.cgi?id=727322
|
|
|
|
|
|
| |
Dark themes need to be debugged, too.
Author: Matthias Clasen <mclasen@redhat.com>
|
|
|
|
|
|
|
|
|
| |
gnome-terminal is still using this setting, so we'll let
applications override it for another cycle. It is no longer
backed by a system-wide setting, though, and it will still
go away eventually.
This partically reverts b26c74e5dac0b5fd869d2c8cc7a0edb6b01aeebd
|
|
|
|
|
|
|
|
|
| |
gnome-terminal is still using this setting, so we'll let
applications override it for another cycle. It is no longer
backed by a system-wide setting, though, and it will still
go away eventually.
This partically reverts 7e3a494fac62140f466fc43f6cc061215953e9b1
|
| |
|
|
|
|
|
|
|
|
| |
This ensures that the initialization for the CSS theme happens when the
style cascade gets queried.
https://bugzilla.redhat.com/show_bug.cgi?id=1064922
https://bugzilla.mozilla.org/show_bug.cgi?id=972382
|
|
|
|
| |
Instead of Return value:
|
|
|
|
|
| |
Without sgml mode, we can't escape /* as /* anymore,
so just switch to // for comments in examples.
|
|
|
|
|
| |
With all element markup gone, it is time to turn off
sgml mode, and get rid of entities as well.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723119
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723119
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This setting will let us keep traditional appearance
of dialogs on platforms where this is expected.
The new setting is called gtk-dialogs-use-header, backed
by the Gtk/DialogsUseHeader xsetting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Applications need a way to fix or adapt the decoration layout,
for situations like split header bars. Setting the layout from
the theme with a style property did not offer a good way to do
this, and the ::show-close-button property does not provide
fine-grained control.
To improve the situation, move the layout string to a property of
GtkHeaderBar which is backed by a setting. This allows platforms to
set a default button layout independent of the theme, while applications
can override the default.
The style GtkWindow style property is now deprecated and ignored.
|
|
|
|
|
|
|
|
| |
Change the GtkSettings default for "shell-shows-desktop" back to TRUE
and also change the default value of the "show-desktop" property on
GtkPlacesSidebar so that the defaultvalue test passes.
https://bugzilla.gnome.org/show_bug.cgi?id=712302
|
|
|
|
| |
This broke tests.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a GtkSetting for whether the desktop shell is showing the desktop
folder icons.
This is on by default because most desktop shells do show the icons on
the desktop. We already have a patch in gnome-settings-daemon to bind
this to the org.gnome.desktop.background show-desktop-icons GSettings
key which is off by default on GNOME.
https://bugzilla.gnome.org/show_bug.cgi?id=712302
|
|
|
|
|
|
|
| |
We add a custom im module for broadway that calls some broadway
specific APIs to show/hide the keyboard on focus in/out. We then forward this
to the browser, and on the ipad we focus an input field to activate
the keyboard.
|
|
|
|
| |
To test with Raleigh much easier.
|
|
|
|
|
|
|
|
|
|
| |
I have been convinced that it is a bad idea to change the behaviour
at the same time as deprecating it, so go back to respecting the
Gtk/ButtonImages xsetting in buttons created with
gtk_button_new_from_stock() when it is set.
The setting as well as the function are still deprecated, and the
default value of the setting will remain FALSE.
|
|
|
|
|
|
|
|
|
| |
I have been convinced that it is a bad idea to change the behaviour
at the same time as deprecating it, so go back to respecting the
Gtk/MenuImages xsetting in GtkImageMenuItem when it is set.
The setting as well as the widget are still deprecated, and the
default value of the setting will remain FALSE.
|
| |
|
| |
|
|
|
|
|
|
| |
We added code to look for settings.ini in system config dirs,
and then proceeded to move it to /usr/share/gtk-3.0 :-(. So,
look in that location as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 4b5a389e88af7e7a1fa9e33294642dcfbc2832ec.
This change caused considerable concern about accidental
leaking of passwords, see e.g.
https://bugzilla.gnome.org/show_bug.cgi?id=706563
https://bugzilla.gnome.org/show_bug.cgi?id=706873
https://bugzilla.redhat.com/show_bug.cgi?id=994237
We may have to do something else for password entries, such
as the windows-style 'peekabo' icon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit b2e666bf8f297eb998331fa8ce0062ce7a5198fa.
We need to keep cursor blinking configurable for accessibility
reasons.
https://bugzilla.gnome.org/show_bug.cgi?id=704134
Conflicts:
gdk/win32/gdkproperty-win32.c
gdk/x11/gdksettings.c
gtk/gtksettings.c
gtk/gtktextview.c
|