c4615eff7b
range: rename function
...
The function queues an allocation now, not a draw.
2016-03-06 11:10:44 -08:00
de1c4bad6f
range: remove duplicated code
...
This is already called by range_grab_add().
2016-03-06 11:10:44 -08:00
d9db329496
scale: trivial code cleanup
2016-03-06 11:10:44 -08:00
f294bdc803
scale: deprecate value-spacing style property
...
Nothing uses it now.
2016-03-06 11:10:44 -08:00
a9b50b6f69
scale: port scale values to gadgets
...
And add a default color like it was before.
This also fixes other issues with scale values interacting with scale
mark labels, which were buggy at least since 3.18.
2016-03-06 11:09:46 -08:00
27b53b58c3
Updated Hungarian translation
2016-03-06 18:27:26 +00:00
94f0cef6fc
Minor documentation improvement
...
https://bugzilla.gnome.org/show_bug.cgi?id=583780
2016-03-06 10:23:49 -05:00
4ab91f09cf
spin button: Limit the entry width to reasonable values
...
When opening the value editor for any GtkAdjustment properties
in the inspector, the popover stretches out for miles, since
it reserves enough space to draw MAXDOUBLE. This is not useful.
Limit the space we reserve to 8 digits.
2016-03-05 23:45:35 -05:00
6d1cdaff7e
gtk-demo: Use <accelerator>
...
Add an example of <accelerator> use in the builder example.
2016-03-05 23:44:03 -05:00
9c0e4c174a
builder: Allow 'primary' as a modifier value
...
Support aliases for flags values in GtkBuilder, and use this
to support the special value 'primary' for GdkModifierType
values.
https://bugzilla.gnome.org/show_bug.cgi?id=699891
2016-03-05 23:44:03 -05:00
27a6183b98
range: simplify calculation
2016-03-05 19:09:18 -08:00
8242182404
range: move declarations to inner block
...
Where they're needed.
2016-03-05 19:09:18 -08:00
990bd03c35
range: use a fixed offset for mark "snap" size
...
Instead of making it dependent on the slider size.
2016-03-05 19:09:18 -08:00
6efe1f411a
Revert "range: use border box for slider area"
...
Since it causes problems with event coordinates.
This reverts commit 0883ff5eed
2016-03-05 19:09:18 -08:00
d866f364d1
Updated Swedish translation
2016-03-05 23:03:05 +00:00
6338c5ee7c
Updated Slovenian translation
2016-03-05 22:37:17 +01:00
4f76a89de0
Updated Slovenian translation
2016-03-05 22:33:50 +01:00
5c248bbd79
Make the settings test fail
...
Small thinko: We only get to see the test artifacts in
continuous if the test fails. So make it fail, temporarily.
2016-03-05 15:49:34 -05:00
31fd41e547
Adwaita: fix glitch in fine-tune scrollbar theming
...
The fine-tune mode should not change the overall dimensions of the
scrollbar.
2016-03-05 12:05:26 -08:00
3608d042e0
Updated Russian translation
2016-03-05 19:56:37 +00:00
bdeff73bec
Updated Slovenian translation
2016-03-05 20:56:06 +01:00
f77407e19a
Updated Slovenian translation
2016-03-05 20:49:05 +01:00
c1b8aee5c2
Updated Lithuanian translation
2016-03-05 21:37:17 +02:00
8f25481406
win32: use a struct for the event source
...
This removes the event_poll_fd global variable and the (ab)use of
get_default_display. It is also more consistent with other backends.
Also store display
2016-03-05 20:31:10 +01:00
58a49c1a4b
win32: fix "unused variable" warning
2016-03-05 20:31:10 +01:00
6066519e73
Updated Brazilian Portuguese translation
2016-03-05 19:05:56 +00:00
d69100547c
testsuite: Remove a test that isn't valid with csd
...
With csd, the allocation of the window will be larger than the
default size, since it includes borders and decorations. Just
remove this check.
2016-03-05 13:47:41 -05:00
b2e6ad640d
Add a test that dumps settings
...
This is not much of a test, tbh. But it will give us a convenient
dump of all GTK+ settings in continuous, which helps with tracking
down test failures that might depend on settings.
2016-03-05 13:41:47 -05:00
434b08fe24
status icon: Prevent size dithering
...
We're seeing loops where the size of some status icons constantly
dithers between 24 and 25. Since I couldn't track down exactly
where the one extra pixel comes from, just stop reacting
to single-pixel size changes.
https://bugzilla.gnome.org/show_bug.cgi?id=758893
2016-03-05 12:15:42 -05:00
213108b64f
Minor cleanup
...
The GtkStatusIcon::size-changed signal expects a boolean return.
2016-03-05 12:11:05 -05:00
8a62a36d2e
Update a11y test output
...
These tests can now assume that the csd header bar will be there.
2016-03-05 10:40:06 -05:00
6ce3c78b7a
Run accessibility tests always with CSD
...
This avoids differences in the output that are caused
by the presence or absence of the header bar.
2016-03-05 10:40:06 -05:00
499c20d85f
Updated Polish translation
2016-03-05 14:47:17 +01:00
154d48ef1a
Update Latvian translation
2016-03-05 12:36:09 +02:00
251810ff40
inspector: Avoid pointless selections
...
The CSS selector and the class hierarchy are purely
informative, no need to select anything here.
2016-03-05 00:35:08 -05:00
e69c1c5a9b
inspector: More grid lines
...
I had forgotten the css property list.
2016-03-05 00:34:39 -05:00
360bad6865
inspector: Some ui refinements
...
Remove pointless expanders from lists, add grid lines and,
in some places, tree lines.
2016-03-05 00:29:06 -05:00
fa36f34fcf
Update expected output of a11y tests
...
The window type attribute shows up here now.
The caret mode changes also affect some tests.
2016-03-04 23:51:39 -05:00
2b1fc6166c
a11y: Expose window type hint as attribute
...
This was an old request, maybe still useful.
https://bugzilla.gnome.org/show_bug.cgi?id=468122
2016-03-04 23:50:50 -05:00
92662828ba
messagedialog: Respect the gtk-keynav-use-caret setting
...
We used to always make the labels in message dialogs selectable,
which is a bit problematic wrt. to keynav - the label can
unexpectedly 'turn blue', which irritates some people.
With the new gtk-keynav-use-caret setting, we can now only
make the labels selectable when it is required for accessibilty
reasons.
2016-03-04 22:44:30 -05:00
d8dee2952a
gdk: Add an X setting for gtk-keynav-use-caret
...
This will let us toggle the use-caret setting session-wide.
2016-03-04 22:44:29 -05:00
5c0b589acd
text view: Respect gtk-keynav-use-caret
...
When the gtk-keynav-use-caret setting is TRUE, make the cursor
visible regardless of the cursor-visible property.
2016-03-04 22:44:29 -05:00
c9371f6a18
Add a gtk-keynav-use-caret mode setting
...
For accessibility reasons, it is useful to have a global setting
that makes carets visible in all text.
https://bugzilla.gnome.org/show_bug.cgi?id=602526
https://bugzilla.gnome.org/show_bug.cgi?id=762799
2016-03-04 22:43:24 -05:00
f3e068bb31
range: avoid setting slider coordinates to negative numbers
...
This can happen if the theme sets a negative margin, but the coordinate
should never be negative.
2016-03-04 18:13:53 -08:00
fce344d31f
range: factor out a function
...
We're going to modify this in the next commit.
2016-03-04 18:13:53 -08:00
7f9223b0c8
gtk-demo: Fix up the inline-toolbar example
...
The inline toolbar in the style classes demo should use
the icons toolbar-style to ensure that the buttons are square.
2016-03-04 20:50:21 -05:00
b84cf5f349
tool button: Update style classes
...
When changing tool button contents according to the toolbar-style
property, we need to update the style classes to ensure that the
visual style matches.
https://bugzilla.gnome.org/show_bug.cgi?id=760560
2016-03-04 20:50:21 -05:00
5a42c2e478
range: fix warning for gadget slider
...
The slider is not HFW/WFH - just pass -1 to get rid of the warnings.
2016-03-04 17:28:53 -08:00
cdc580463e
gtkwindow: default size with fixed size windows
...
Allow fixed size windows with a default size to grow or shrink as the
content requires, but not smaller than the given default size.
https://bugzilla.gnome.org/show_bug.cgi?id=762974
2016-03-04 20:17:50 -05:00
046a4a6e0f
gtkapplication-dbus: use application id instead of prgname for SM
...
gnome-session takes an "app id" for client and inhibitor registration,
This app id is supposed to be a desktop file id (complete with the
.desktop extension), but gtk+ currently uses g_get_prgname ().
This commit changes gtkapplication to use the application id instead,
which is a much more natural fit. gnome-session is going to be updated
to stop using the .desktop extension, too, so everything is consistent.
https://bugzilla.gnome.org/show_bug.cgi?id=763106
2016-03-04 20:17:26 -05:00
