- 01 Jun, 2016 7 commits
-
-
Bastien Nocera authored
What it should look like: Bold ---- /Size/ x 0.5 x 1.0 What it looks like: Bold /Size/ ---- x 0.5 x 1.0 https://bugzilla.gnome.org/show_bug.cgi?id=767108
-
Matthias Clasen authored
This is now done in GDK, so we can just use the input type here. https://bugzilla.gnome.org/show_bug.cgi?id=767100
-
Matthias Clasen authored
This uses the same heuristics that are currently used in GtkScrolledWindow. https://bugzilla.gnome.org/show_bug.cgi?id=767100
-
Matthias Clasen authored
Having this as an input source type will let us do the heuristics in the GDK backends. https://bugzilla.gnome.org/show_bug.cgi?id=767100
-
Matthias Clasen authored
-
Olivier Fourdan authored
GtkHeadeBar checks the window type hint to determine if the regular buttons such as menu, maximize or iconify should be visible in the header bar. However, an application may very well use a "normal" toplevel window and set it transient and modal afterwards. In such a case, the iconify button would remain visible, and the user can hide the window, but being a modal, the parent window would remain insensitive. Check for the window type, modality and transient relationship to decide whether or not the regular toplevel buttons should be visible in the header bar. https://bugzilla.gnome.org/show_bug.cgi?id=767052
-
Matthias Clasen authored
Print human readable names for axes and axis sources.
-
- 31 May, 2016 7 commits
-
-
Matthias Clasen authored
-
Matthias Clasen authored
We could just as well remove these calls here, since they have no effect.
-
Matthias Clasen authored
...and deprecate it, recommending GtkStack as an alternative.
-
-
Timm Bäder authored
Draw them inside of the icons, which is where the text scrolls.
-
Matthias Clasen authored
We don't want to maintain this information in two places, so just link to the online documentation here.
-
Matthias Clasen authored
This was causing navigation in the online docs to be confused.
-
- 30 May, 2016 12 commits
-
-
Matthias Clasen authored
When we emit ::draw, the widget should not have alloc_needed set anymore. If this happens, it indicates a broken situation. Add a warning to help tracking down why this might occur. See https://bugzilla.gnome.org/show_bug.cgi?id=765410
-
Matthias Clasen authored
Update the font: syntax to follow css.
-
Timm Bäder authored
-
Daniel Mustieles García authored
-
Timm Bäder authored
Make sure it's obvious what if block it belongs to.
-
Timm Bäder authored
Show only the currently visible child to a11y.
-
Timm Bäder authored
The type is used in widget-factory.ui, so add a dummy definition here to keep the test working.
-
Cédric Valmary authored
-
Cédric Valmary authored
-
Lapo Calamandrei authored
since it doesn't always inherit 'color' color as it should.
-
-
Theppitak Karoonboonyanan authored
-
- 28 May, 2016 2 commits
- 27 May, 2016 4 commits
-
-
-
Theppitak Karoonboonyanan authored
-
Rico Tzschichholz authored
This avoids an unconditional use of XRandr symbol.
-
-
- 26 May, 2016 6 commits
-
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
This is one of the properties that need to be explicitly set.
-
Tiago Santos authored
-
Emmanuele Bassi authored
Initialize the `nearest` variable.
-
LRN authored
When filechooer is re-used (instead of being created and destroyed every time it's needed), it might happen that the directory the application wishes to initially show is the same directory that was shown last time the filechooser was used. In that case, make sure filechooser knows that it does not need to do its default "select $pwd or $home" routine. https://bugzilla.gnome.org/show_bug.cgi?id=766122
-
- 25 May, 2016 2 commits
-
-
Matthias Clasen authored
-
Friedrich Herbst authored
-