OSD timeouts need revisiting

[gigem]

Most OSD displays would probably be OK with a standard timeout or even require user action to clear them, but IMO, there is a small subset which I still feel the timeout should have some reasonable configurability.

[beirdo]

Flows out of #724, which was about OSD timeouts being inconsistent.

[beirdo]

Talking with sphery on IRC, we came up with a proposal to make three types of timeouts, short/medium/long with default timeouts of 3/5/10s. These could be made overridable by either a base theme edit, or by UI-based settings. These three types should adequately cover the entirety of our timeouts, while allowing for some things to last longer than others, etc.

[markk]

ref r25465

[davespmyth@…]

I have a patch (tested) for osd.cpp which allows environment variables to specify the short, medium, and long timeout values. The current values are used if the env vars aren't defined. Should I add the "diff -c" output to this ticket as an attachment?

[stuartm]

Michael, is this still something you are looking at? Is it still relevant?

[sphery]

Yes, I'm still working on this.

[Peter Bennett]

OSD timeouts are: short: 3 seconds, medium: 5 seconds, long: 10 seconds, none: does not timeout. Each OSD screen gets one of these set by the program.

For OSD nav, I set the timeout to long. If paused, the timeout is set to none.

Is there still some need to customize this? They could be added to settings.