After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 560179 - Please make use of gtk-cursor-blink-timeout
Please make use of gtk-cursor-blink-timeout
Status: RESOLVED WONTFIX
Product: gnome-power-manager
Classification: Deprecated
Component: general
2.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-11-10 16:17 UTC by Josselin Mouette
Modified: 2012-03-16 11:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Josselin Mouette 2008-11-10 16:17:45 UTC
It would be nice if g-s-d made use of the cursor blinking timeout introduced in GTK+ 2.12.

The approach I’d like to suggest is to make this timeout depend on the power status. When on AC, disable the timeout. When on battery, make it a few seconds.
Comment 1 Bastien Nocera 2010-10-13 17:57:06 UTC
What's the use of an interface feature like that changing when you're on battery and not?
Comment 2 Josselin Mouette 2010-10-14 12:22:41 UTC
The reason for introducing this change in GTK+ is that having the cursor blink introduces more interrupts, and therefore should be avoided when trying to minimize power consumption.
Comment 3 Bastien Nocera 2010-10-14 12:27:23 UTC
(In reply to comment #2)
> The reason for introducing this change in GTK+ is that having the cursor blink
> introduces more interrupts, and therefore should be avoided when trying to
> minimize power consumption.

Not really, it's for people who prefer to save energy, whether plugged in or not, and don't want to see a blinking cursor in the first place.

Punting to gnome-power-manager. This would involve changing a GSettings key on change of power state. The idea seems profusely confusing to me, and of doubtful benefits.
Comment 4 Richard Hughes 2010-10-14 13:23:11 UTC
This isn't the kind of setting I really want to change on AC state. The laptop doesn't want to work "slower" (either actually, or visibly) when on battery power, as this gives the impression we're offering a degraded service compared to when on AC power.

Ideally, we just nuke things that blink. There's really no real need, and it just costs power.