| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Since it turns out that x/yalign can't be quite equivalently
replaced by h/valign, bring them back as label properties, so
we can eventually get rid of GtkMisc.
https://bugzilla.gnome.org/show_bug.cgi?id=735841
|
| |
|
|
|
|
|
|
| |
Use U+201C/U+201D for quoting.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use U+2013 for ranges.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use U+201C/U+201D for quoting.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Avoid `' quoting.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Always quote drive/volume names.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
No double space after .
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
|
| |
Use a small space before %. This matches what we do for percentages
elsewhere.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
|
| |
At the same time, use a small space before %.
This matches what is done in GtkCellRendererProgress.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use a small space before %.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
|
| |
No `' looks just terrible. For quoting in non-UI contexts, we
prefer either '' or "".
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use U+201C/U+201D for quoting, and use U+2019 instead of apostrophe.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use U+007D MULTPLICATION SIGN for dimensions.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
| |
Use U+2236 RATIO instead of ':' for times.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
|
|
|
|
|
|
|
|
| |
Use U+00D7 MULTIPLICATION SIGN instead of a plain old x in
paper names, following https://wiki.gnome.org/Design/OS/Typography.
This is a string change.
https://bugzilla.gnome.org/show_bug.cgi?id=735192
|
| |
|
| |
|
|
|
|
| |
We were forgetting to include some theme files.
|
|
|
|
|
|
|
|
| |
This adds both a compile time check for the SDK version being
compiled against, as well as a runtime check in the case the
resulting binary is run against an older SDK.
https://bugzilla.gnome.org/show_bug.cgi?id=735054
|
|
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=737517
|
|
|
|
|
| |
And fix the messy style we have for *:link in the process.
https://bugzilla.gnome.org/show_bug.cgi?id=737386
|
| |
|
|
|
|
|
|
| |
Add some docs/example about the possible event handling ordering issues
that may appear on GtkGesture::begin between multiple gesture groups.
Mostly relevant for state changes.
|
|
|
|
| |
- Some simple instructions for future SASS/ruby lovers
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The remaining code assumes that the dialog doesn't get destroyed, but
it actually does on delete-event.
In particular, the filter function and the preview text are lost as
soon as the dialog is created and thus when we create a new dialog we
don't have those properties to set on it anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=719936
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 5744bb3cf16cabfe4ee4677c7250ee8f90550a37.
This causes conflicts with already existing shortcuts e.g.
in gedit.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This test makes sure that out heuristic for finding
get_type functions works as expected.
https://bugzilla.gnome.org/show_bug.cgi?id=635258
|
|
|
|
|
|
|
|
|
| |
Factor out the typename-to-get-type mangling as a separate
function, for easier testing.
Also fix some cases where it doesn't, currently, like
GString -> g_string_get_type and
GdkRGB -> gdk_rgb_get_type
|
|
|
|
|
| |
This has been requested in
https://bugzilla.gnome.org/show_bug.cgi?id=708206
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The scale in the selectable listbox in page 2 of gtk3-widget-factory
has the flaw that the row is getting selected even when one only
interacts with the scale - unlike e.g. the checkbutton and button
further down in the listbox.
The problem is that GtkRange is trying to claim the sequence for
the drag gesture from the ::pressed handler of a multipress
gesture. Since the drag gesture hasn't seen the sequence at this
point, that is ineffective.
The fix here is to rearrange the gestures so that the multipress
gesture sees the sequence before the drag gesture, and then
claim the sequence from the ::drag-begin handler.
|
| |
|
|
|
|
|
|
| |
This was clearly an oversight - the function claims the sequence
at the end, and for the popup menu case, we have an early exit
that misses this.
|
|
|
|
|
| |
This will let us tweak stuff that gets shown in fullscreen windows,
https://bugzilla.gnome.org/show_bug.cgi?id=654051
|
|
|
|
|
| |
Pointed out by Garrett Regier in
https://bugzilla.gnome.org/show_bug.cgi?id=737439
|
|
|
|
| |
It doesn't make sense to have them work in entries, but not here.
|
| |
|
|
|
|
|
| |
Add a Ctrl-k binding too, and make them match their traditional
commandline meaning or 'erase line to the beginning/end'.
|
|
|
|
|
| |
Ctrl-u is a fine, well-established keybinding for this purpose,
lets just use it.
|
|
|
|
| |
No need to loop toplevels in two places.
|
|
|
|
|
|
| |
The delay was a mistaken attempt to work around a problem that
is now better understood, see
https://bugzilla.gnome.org/show_bug.cgi?id=735338
|
|
|
|
| |
No need to check the same widget twice in a row for being a window.
|
|
|
|
|
|
| |
Binding signals can return a boolean indicating whether they
handled the event. Use that here and return FALSE if the
inspector keybinding is disabled.
|
| |
|