Opened 14 years ago
Closed 11 years ago
#9706 closed Patch - Feature (Won't Fix)
Theme Control of OSD Timeout Values
| Reported by: | Owned by: | sphery | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - Video/OSD Rendering | Version: | 0.24-fixes |
| Severity: | low | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Uses theme "osd.xml" file to override the default short, medium, and long OSD timeout values.
Default values are still used if no override values are found, or if the override values are invalid.
Can be easily extended to include new OSD timeout values if/when they become defined.
Attachments (4)
Change History (6)
Changed 14 years ago by
| Attachment: | osd.cpp.diff added |
|---|
Changed 14 years ago by
| Attachment: | xmlparsebase.cpp.diff added |
|---|
Changed 14 years ago by
| Attachment: | xmlparsebase.h.diff added |
|---|
Changed 14 years ago by
| Attachment: | xmlparsebase.cpp.2.diff added |
|---|
comment:1 Changed 14 years ago by
| Owner: | changed from markk to sphery |
|---|---|
| Status: | new → accepted |
comment:2 Changed 11 years ago by
| Resolution: | → Won't Fix |
|---|---|
| Status: | accepted → closed |
I think this is the wrong approach. Either these values are controlled by the user through settings, or my preferred approach is that we used fixed defaults that work for everyone. The OSD can always be dismissed early by the press of a button.
Having the theme set the timeouts just doesn't make much sense to me, should a user have to change their entire theme just to read the OSD before it disappears? What happens when the theme they prefer visually uses timeout values that are just too short?
Corrected function name in QString call.