| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This is in preaparation for the big GtkCssComputedValues => GtkCssStyle
rename
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I removed it in 14f5ce710856708dc80fcc98cb5eb2ba257f34ad because I
thought it was unnecessary, but it wasn't. When we build a tree like
this:
.matches ─┬─ .doesntmatch
└─ .alsodoesntmatch
We would get the changes for the .matches part returned. This is however
only right if that node of the tree contains results. If results only
exist with the child nodes (all of which don't match), then this part
should not match either.
|
|
|
|
|
| |
We want to keep matching as long as selectors are simple. Otherwise we'd
never be matching, because the first selector is always simple. Oops.
|
|
|
|
|
|
|
| |
The notify for "size" and "size-points" properties
are inverted.
https://bugzilla.gnome.org/show_bug.cgi?id=742311
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkCalendar can have an invalid date — mostly at initialization. This
means that GDateTime construction may fail. We need to handle that case
gracefully, like the old code did.
This fixes the `notify` test suite, which started failing with:
/Notification/GtkCalendar:
GLib-CRITICAL **: g_date_time_get_day_of_week: assertion 'datetime != NULL' failed
inside the Continuous builder.
|
|
|
|
|
|
|
| |
This appears to have accidentally used the normal keypresses twice instead
of the KP variants. This resulted in shift+insert pasting twice.
https://bugzilla.gnome.org/show_bug.cgi?id=742170
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This helps diagnose e.g. csd problems.
|
|
|
|
| |
No wonder nobody has tried my awesome magnifier yet...
|
| |
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
| |
|
|
|
|
|
|
| |
The major version is set twice.
https://bugzilla.gnome.org/show_bug.cgi?id=741954
|
|
|
|
|
|
|
|
|
|
|
| |
Sending backingScaleFactor to a NULL NSWindow will silently give the
value 0 for the scale factor, causing insidious divide-by-zero bugs down
the line. This checks if the NSWindow is NULL first, as seems to happen
throughout the rest of the file.
Note that I don't have a hi-DPI OS X machine to test this on, though.
https://bugzilla.gnome.org/show_bug.cgi?id=738338
|
| |
|
|
|
|
|
| |
This way transient mouse movements over scrollbars don't cause flickering,
and more spaced movements have it enabled shortly.
|
|
|
|
|
| |
Only horizontal coordinates are checked for the vertical scrollbar, and
vice versa.
|
| |
|
|
|
|
|
|
| |
This is so we can detect crossing events on the scrolledwindow widget,
which can be useful for toggling certain behaviors or not depending on
whether the mouse is on the widget.
|
|
|
|
|
| |
On mice, scrollbars are always triggered temporarily. On proximity to an
scrollbar, it will be switched to full-width.
|
| |
|
|
|
|
|
|
|
|
|
| |
If the first of the month was falling on a Sunday, we would not
render any days of the previous month, and instead show two weeks
of the next month at the bottom. Improve this by showing one week
of each.
https://bugzilla.gnome.org/show_bug.cgi?id=301835
|
|
|
|
|
|
| |
When changing between months, we can get into a situation like
'February 30", which GDate doesn't accept. Don't crash in that
case.
|
|
|
|
|
|
|
|
| |
Changing font size does not cause widgets to update their size
properly anymore, since we forgot an invalidation flag. The
problem can be observed e.g. by running gtk3-demo and calling
gsettings set org.gnome.desktop.interface font-name "Cantarell 22"
|
|
|
|
|
| |
The days that are not in the current month used to be rendered
in a ligher color. This was lost at some point. Bring it back.
|
|
|
|
|
| |
Instead of old copy-paste code, use GDateTime to determine week
numbers and days of week.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
On the wayland backend, set up GDK_WINDOW_SUBSURFACE windows
for popovers. In the popover code, the popover-relative-to-parent
calculation had to be tweaked, and it's been made to always prefer
the given popover position, since there's no sizing limitations.
https://bugzilla.gnome.org/show_bug.cgi?id=738891
|
|
|
|
|
|
| |
gtk_builder_add_from_string takes more than 2 parameters.
https://bugzilla.gnome.org/show_bug.cgi?id=741897
|
|
|
|
|
| |
The WM already adds the window shadow in that case, so just use the
box-shadow to add the border here.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=477454
|
|
|
|
|
|
|
|
|
|
| |
We were asserting priv->filename != NULL in various places,
which leads to apps refusing to work when HOME is set to a
nonexisting or nonwritable value. Since it isn't hard, just
make GtkRecentManager survive without a filename. We won't
save or read any recently used files in this state, but
thats ok.
https://bugzilla.gnome.org/show_bug.cgi?id=739038
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Provide a mechanism for hiding the "Quit", "About" and "Preferences"
menu items from the normal places in a traditional menubar layout (in
the File and Edit menus) when the menu is being rendered in the Mac OS
menubar.
These items can already be found in the application menu.
With this feature, applications can now define a single menu to use in
all 'traditional' scenarios.
Use this new attribute in Bloatpad.
https://bugzilla.gnome.org/show_bug.cgi?id=741610
|
|
|
|
|
|
| |
This apparently used to work, and it doesn't do harm to allow it.
https://bugzilla.gnome.org/show_bug.cgi?id=705582
|
| |
|