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 667673 - Setting GApplication inactivity-timeout to 5s is a bit weird
Setting GApplication inactivity-timeout to 5s is a bit weird
Status: RESOLVED OBSOLETE
Product: yelp
Classification: Applications
Component: General
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2012-01-11 08:30 UTC by Vincent Untz
Modified: 2018-05-22 12:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Untz 2012-01-11 08:30:06 UTC 
I'm not sure why yelp sets the inactivity-timeout to 5s:

 - if you start yelp from the command line, it's annoying
 - if you start yelp from the launcher, you won't start 5s after leaving the only window you have
 - if you start yelp from a help menu, I don't think you'll come back to the help less than 5s after closing the window

I guess there's a rationale, but I'm missing it. In the meantime, users starting yelp from a terminal are annoyed :-)
Comment 1 Matthias Clasen 2012-01-11 12:13:47 UTC 
Starting from a terminal should not be the deciding factor when considering how to improve the user experience of a graphical application. But I agree that 5s seems too little to make any difference.
Comment 2 Bin Li 2012-01-12 03:22:52 UTC 
Matthias,

 What's the reason to set inactivity-timeout? I still a little confused. Thanks!
Comment 3 Matthias Clasen 2012-01-13 12:17:53 UTC 
The reason is so that the process is already around and can be reactivated quickly if the user needs it again.
Comment 4 GNOME Infrastructure Team 2018-05-22 12:56:35 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/yelp/issues/57.