Opened 11 years ago

Closed 19 months ago

#8701 closed Developer Task (Abandoned)

OSD timeouts need revisiting

Reported by: gigem Owned by: sphery
Priority: minor Milestone: unknown
Component: MythTV - User Interface Library Version: Master Head
Severity: medium Keywords: osd timeout settings
Cc: Ticket locked: no


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.

Change History (11)

comment:1 Changed 11 years ago by beirdo

Version: UnspecifiedTrunk Head

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

comment:2 Changed 11 years ago by 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.

comment:3 Changed 11 years ago by markk

ref r25465

comment:4 Changed 11 years ago by robertm

Status: newassigned

comment:5 Changed 11 years ago by stuartm

Owner: changed from stuartm to sphery

comment:6 Changed 11 years ago by stuartm

Owner: changed from sphery to sphery

comment:7 Changed 11 years ago by 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?

comment:8 Changed 10 years ago by stuartm

Type: taskDeveloper Task

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

comment:9 Changed 10 years ago by sphery

Yes, I'm still working on this.

comment:10 Changed 3 years ago by 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.

comment:11 Changed 19 months ago by Mark Kendall

Resolution: Abandoned
Status: assignedclosed
Note: See TracTickets for help on using tickets.