Opened 15 years ago
Closed 14 years ago
#5888 closed enhancement (wontfix)
configure OSD input timeout before a channel number will be committed
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - General | Version: | head |
| Severity: | low | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Currently you have to wait for get browse informations (or change channel without press return key) for all non-unique channel numbers after entering the digit(s) until the osd fade-out was done.
Now you can configure (Playback OSD screen) the maximum time to wait after entering a digit to commit the input queue.
Attachments (1)
Change History (4)
Changed 15 years ago by
| Attachment: | osd_input_timeout_trunk@18947.diff added |
|---|
comment:1 Changed 15 years ago by
| Component: | mythtv → MythTV - General |
|---|---|
| Status: | new → infoneeded_new |
comment:2 Changed 15 years ago by
i want to switch faster to other channels (with channum > 9) by don't wait till fadeout of the OSD before commit the entered number to the input_queue. e.g.: start EPG-browse and press 1 + 9 on your remote it should be less then 300ms to see the EPG from channel 19. same for starting a channel change. I think the fadeout of the entered number can be removed completely.
But you can close this ticket. I will take a look after OSD->mythui port at this again. Currently i don't use this ticket by my self and therefore can't provide actual patches for trunk. If you write another solution for faster switching the EPG-Browse (e.g. remove the fade completely) this will be fine too.
comment:3 Changed 14 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | infoneeded_new → closed |
Closed at submitter request, and in anticipation of the new MythUI OSD.
Hmm, more settings ... Markus are you using this to reduce or increase the time we currently wait? Can this be improved without adding an additional setting?
We plan on removing the existing OSD timeout settings if that helps to explain why we don't want more OSD timing related settings.