Opened 21 years ago
Closed 21 years ago
#731 closed enhancement (invalid)
Unify playback and livetv infoOSD, add small and large proginfo OSDs
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
This patch modifies playback in mythtv tv_play such that WatchingLiveTV, WatchingRecording, and WatchingPreRecorded all call the same method to toggle the OSD. In addition it adds support for multiple program_info OSDs. The pseudocode for which is displayed looks something like this:
WatchingLiveTV:
On INFO command
If nothing displaying
If has smallinfo
display smallinfo
Else
display longinfo
Else If smallinfo displaying
If has longinfo
display longinfo
Else
HideAll
Else If longinfo displaying
HideAll
WatchingPlayback:
If nothing displaying
display status
If status displaying
Use WatchingLiveTV logic
It also adds some utility functions OSD::IsSetDisplaying() and OSD::HasSet().
Side effects:
TV::ToggleOSD now takes param (bool includeStatusOSD)
renames TV::UpdateOSD to TV::UpdateOSDProgInfo
removes TV::DoInfo (replaced with ToggleOSD)
Attachments (1)
Change History (6)
by , 21 years ago
| Attachment: | unified-multiple-proginfoosd.diff added |
|---|
comment:1 by , 21 years ago
Would make sense to have the large OSD scale vertically to be able to show as much as possible of the description, of course stopping if it runs out of space.
comment:2 by , 21 years ago
You'd think so, but the problem comes when you're trying to automatically figure out how to stretch what part of your background image.
http://capnbry.net/~bmayland/fi/pvr150/osds/tivo2lgbanner.jpg
Maybe if the osd designer was required to break up the image into scalable and non scalable portions, it would be possible.
comment:3 by , 21 years ago
Is the max length the description can be reasonable? Could the OSD that contains the description be sized for that max length always like how TiVo does it?
comment:4 by , 21 years ago
Yeah of course the OSD would need to be splitted into maybe three parts: Top, Middle (which is repeated, not scaled) and Bottom.
comment:5 by , 21 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
"Discuss" ideas on the mailing lists. Do not use the bug database as a message board.

Patch agains svn r8080