Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#320 closed patch (fixed)

Dialog informing user that they should have gotten a signal by now

Reported by: danielk Owned by: danielk
Priority: minor Milestone: 0.19
Component: mythtv Version: head
Severity: medium Keywords:
Cc: Ticket locked: no


After a certain time (perhaps set using the #319 feature) I'd like to have the frontend pop-up a dialog informing the user of their options, such as changing the channel, tuner, timeout etc. Right now some users are confused when nothing happens when the tune did not succeed, and assume that MyhtTV is stuck when it actually is just waiting for user input.

Attachments (1)

fix320-v1.patch (7.3 KB) - added by danielk 15 years ago.
a rough around the edges fix for this

Download all attachments as: .zip

Change History (5)

Changed 15 years ago by danielk

Attachment: fix320-v1.patch added

a rough around the edges fix for this

comment:1 Changed 15 years ago by danielk

Milestone: unknown0.19
Status: newassigned
Type: enhancementpatch

This isn't quite ready, it hits the DB 5 times and it really shouldn't have to...

comment:2 Changed 15 years ago by danielk

Resolution: fixed
Status: assignedclosed

Closed by revision [7344].

Basically it fetches the channel_timeout from the DB, and if it takes longer than that to start getting data from the backend it pops up an informational dialog.

The change in mythdialog is to add MythMainWindow??::GetKey?() which is symmetric to RegisterKey?(). It fetches the key binding from the database for display in informational dialogs like the above. This lets you tell the user exactly what key to press, even if they have remapped the keys.

comment:3 Changed 15 years ago by danielk

(In [7427]) Fixes #320.

This fixes two additional problems that cause lost follow on recordings:

  • Overrecord race problem, an old problem that was made worse by event loop improvements.
  • Clock drift problem, another old problem.

Fixing the clock drift problem required a MythTV protocol change so you must upgrade all your backends & frontends. Basically, it adds a GET_CURRENT_RECORDING query so that we can find out if the slave backend is recording something the master backend thinks should be done by now.

It is still important to keep the backend clocks in sync with something line NTP, but with this commit minor clock drift will only mean you might lose a few seconds of you recording, not the entire follow on recording.

The overrecord race problem is also made worse by a clock drift, basically if the slave is over 2 seconds "slower" than the frontend you almost always lost the race, otherwise you lost the race in rough proportion to how far you were out of sync with the master backend's clock.

comment:4 Changed 15 years ago by danielk

Sorry, [7427] closes #430, not #320.

Note: See TracTickets for help on using tickets.