Choosing Ctrl for window movement messes up selecting mutiple
entries in list and grid widgets (e.g. files in nautilus) so
don't offer it as an option. Closes bug #409405.
The code treated a URI as a path which would result in escaped
characters showing up as "%20" and such in the destination file
name. Be more careful to treat URIs as URIs and paths as paths.
Closes bug #603732.
Set the has-tooltip property to enable tooltips on items in the background
chooser.
Also remove the custom tooltip timeout value so that it is now consistent
with the rest of the desktop.
Patch from: Matthias Clasen <mclasen@redhat.com>
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=596369
Clarify the background style options as per the suggestions in bug 411048
by making all the descriptions the same tense and replacing "Fill screen"
with "Stretch".
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=411048
From bug 594709:
The desktop file for the theme installer doesn't have OnlyShowIn=GNOME;
This prevents it from working with Firefox (apparently) and it seems like it
should have it anyway.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=594709
Touchpads that can't do two-finger cannot two-finger scroll - disable this
scroll method.
Touchpads that don't have physical buttons mustn't disable tapping - set to
on by default and disable checkbox.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This patch does 2 things:
1) Defines a DrwTimer that we use instead of GTimer. This is just a thin
wrapper around g_get_current_time, and it means we can accurately track
typing/idle periods based on real-world wall-clock time, which GTimer is
apparently not intended to do.
2) The typing monitor has some complicated state handling where it transitions
between an IDLE state and a TYPING state. This transition is based on running a
callback once per second, and checking whether any keystrokes have been
recorded since the last time the callback was called. The actual idle *time* is
tracked separately, independently of these two states, but only when we are in
the IDLE *state* was the idle *time* checked to see if we should reset the
break timer. This leads to a race condition -- if we suspend while in the
TYPING state, then eventually we will wake up, notice that no key press has
happened in the last second, *reset the idle timer*, transition to the IDLE
state, and then check the amount of time on the idle timer. We will thus never
notice the amount of time that the computer was suspended.
I considered making the IDLE/TYPING transition code smarter, but it turns out
the desired behavior for the two states is entirely identical anyway, so rather
than adding more complexity to this pointless code, I just diked it out and
replaced them both by a single state called RUNNING.
Closes bug #430797.
When the typing break screen is displayed and break postponements are enabled,
there is a 500ms delay before the 'Postpone' button becomes sensitive.
Increase that delay to 5000ms (5s).
Rationale:
When I'm really focused on something I will click the 'Postpone' button, or
even use the keyboard short-cut Alt-P, so that I can carry on with what I was
doing. Then later I won't even remember having done it. This can happen
several times in a row. I'm sure it happens this way for other people too.
With a 5s delay before a break can be postponed it gives the user time to think
about whether they really need to carry on with what they were doing or if it
can wait after all.
Closes bug #597086.
At least
* gnome-keybinding-properties
* gnome-about-me
* gnome-appearance-properties
* gnome-theme-test
* gnome-font-viewer
need it, so just add it to the list of common modules (bug #600589).
