| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
These things are necessary to work on the Adwaita theme,
so include them in the tarball.
|
|
|
|
| |
These css files were optimized away a few commits ago.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since this is now builtin, we don't need the extra redirection
anymore.
|
|
|
|
|
| |
These were imported from gnome-themes-standard, but are not
referenced from the css.
|
|
|
|
|
| |
This ensures that GTK+ applications have a high-quality theme on
all platforms, and look consistent.
|
|
|
|
|
| |
This adds the resources for the Adwaita theme, and includes them
in libgtk, on all platforms.
|
|
|
|
|
| |
No need to carry around these resources when we are not
going to use them.
|
|
|
|
|
| |
This will help when including Adwaita. It will also let us
drop the win32 theme on Linux, hopefully.
|
|
|
|
| |
This allows us to get rid of some aliases in the .gresource.xml.
|
|
|
|
| |
Preparing for Adwaita to come in here.
|
| |
|
|
|
|
| |
Recommended by Allan Day.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The former can be called individually on each sequence, and the latter will
always call the former on all currently active sequences, so only implementing
resetting on cancel() works for both cases. Also, chain up on subclasses
implementing cancel.
This fixes clicking on nautilus' file list after popping up a menu, as broken
grabs are one of those situations where sequences get cancelled individually,
the "current button" wasn't properly reset, and further clicks with button != 3
were ignored.
|
|
|
|
|
|
|
| |
This used to be done before the gestures port, and was removed
accidentally, so keep the motion_notify_event handler just for
this, and fallback to having those events handled by gestures
too.
|
|
|
|
|
|
|
| |
The annotations were intended for the return
value, not the instance argument.
https://bugzilla.gnome.org/show_bug.cgi?id=731299
|
|
|
|
|
|
| |
Reported by andlabs in irc://irc.gnome.org/gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=731382
|
| |
|
|
|
|
|
| |
This helps in separating message dialogs from other dialogs,
theming-wise.
|
| |
|
|
|
|
|
| |
Scrollbars might be a bit too narrow for touch (and generally less useful
besides kinetic scrolling), but those should be functional nevertheless.
|
|
|
|
|
|
|
|
|
|
| |
This way plain clicks can be handled in gtkmain through the usual delivery mechanism,
and get possibly handled too by widgets holding a GTK+ grab. If window dragging is to
be started, the sequence will be claimed (and a grab will happen afterwards), notifying
properly the grabbing widget that event delivery was interrupted.
This makes it possible to dismiss popovers by clicking on window headerbars, while
still making it possible to drag the window with the popover opened.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Weston numbers its touch sequences ids starting from 0, thus simply
setting the GtkEvents touch.sequence to the touch id value typically
causes gdk_event_get_event_sequence to return NULL. Unfortunately this
confuses other parts of GDK.
As both weston & mutter keep the sequence id between 0..max_dev_touches
-1 simply use + 1 to keep the id > 0. While this isn't entirely correct
(compositor could send -1 as the touch id), this keeps the touch id in
gtk tied to the touch id from weston which is useful for debugging. A
more thorough solution could be done when it turns out this is an issue
in practise
https://bugzilla.gnome.org/show_bug.cgi?id=731371
|
|
|
|
|
| |
Check that loading symbolics works, even if the symbolic is only
available in a fixed size.
|
| |
|
|
|
|
|
|
| |
Reported on irc://irc.gnome.org/gtk+ by Rena.
https://bugzilla.gnome.org/show_bug.cgi?id=731377
|
|
|
|
|
| |
We don't support multiple screens anymore, so there is no need
for marking API as multihead safe any longer.
|
|
|
|
| |
These should just be replaced by CSS margins, etc.
|
|
|
|
|
|
| |
The non-zero default default-border was causing buttons to shrink as
the focus moves around them. Themes which want a default-border should
define it explicitly.
|
|
|
|
|
| |
It turned out not all code was fully prepared to handle multiple buttons,
this avoids respawning https://bugzilla.gnome.org/show_bug.cgi?id=731020.
|
|
|
|
|
|
| |
The code is actually prepared for that, the gesture was initially limited
to only handling GDK_BUTTON_PRIMARY because it only used to handle row
activation.
|
|
|
|
|
| |
These variables were last used before moving row activation to being
managed by a gesture.
|
|
|
|
|
|
|
|
|
| |
The multipress gesture on the bin window now also does all the business related
to row selection. As row selection and activation can't be easily decoupled, this
fixes certain problems around ::row-activated being emitted on NULL paths.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=731455 and
https://bugzilla.gnome.org/show_bug.cgi?id=731018
|
|
|
|
|
|
| |
This gesture acts only on events from the bin window, and checks that
either the pressed row is draggable, or the conditions for rubberband
selection apply.
|
|
|
|
|
|
| |
A multipress gesture takes care of autosizing on double click, and
a drag gesture is used for both column dragging/resizing (only one
can happen at a time).
|
|
|
|
|
| |
This happens in an event handler, and the button event should be
expected to have the right coordinates on the event window already.
|
|
|
|
|
|
|
| |
touch/button release
This makes gtk_gesture_get_current_button() work properly on GtkGesture::end, and signals
spawn from there on subclasses.
|
|
|
|
|
|
| |
We need to show child windows and handle in the right order,
otherwise the input-only handle window ends up under the children
where it is useless.
|
|
|
|
|
|
|
| |
When placing tooltips, the csd shadow will get 'pushed up' and
may end up underneath the pointer. We don't want this to cause
the tooltip to be hidden, because that leads to flickering, so
ignore the shadow when finding the widget under the pointer.
|
|
|
|
|
|
| |
For csd override-redirect windows, we don't set up resize handles,
but we were not ignoring the margin in all places, causing some
size calculations to go wrong.
|
|
|
|
| |
GtkText, GtkList and GtkCList don't exist anymore.
|
|
|
|
|
| |
It's now just a GtkCssComputedValues + refcount. And
GtkCssComputedValues has its own refcount, so use that one instead.
|
|
|
|
|
|
|
|
|
|
| |
... from per style data to only existing once per style context. This is
technically an API break because it no longer allows getting different
style properties between save()/restore() pairs, but I don't think this
was ever intended to work that way, as the style property API was to be
used and is used via gtk_widget_get_style().
And it simplifies code a lot.
|
| |
|
|
|
|
|
| |
The file was forgotten in 98954bd1d1e27e2e8b5181af1752a9e8e107c74c and
caused test failure. Oops.
|
|
|
|
|
| |
It evaluates to "current state" in all cases, so no need to special case
it.
|
| |
|