Graphical EPG losses position with timer manipulation

Issue #172 resolved
Ian Brabham created an issue

When manipulating timers the Graphical EPG losses the current event position. The event position should always be maintained for all manipulation, i.e. doing an "Info" does not lose the event position.

The issue is somewhat symptomatic in that the event hour:minute seems to be maintained but the day component is reset to the current day.

To further confuse matters further using the "9", move to prime time feature while viewing events for a future day, will correctly move to the configured prime time for that day and as a side effect set the day component reset value to that day. I currently use this as a hack around for more easily entering multiple timers on future days.

Using the "5", move to current time feature, also has the same side effect of setting the day component reset value to the current day.

A downside of using this "9" hack to trick the reset day value is the "4", move to previous event page, will not move back beyond the Prime Time of the reset value day.

Reproduction steps

Enter the Graphical EPG.

Navigate to a future time, i.e tomorrow.

Add a timer, i.e. Record, Green or Blue.

When done the event region displayed is reset to current day.

Comments (10)

  1. IanSav
    • removed issue_status

    I don't think the time jumps are as predictable as Ian posted. Some of the jumps defy explanation.

  2. IanSav
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from New to Confirmed.
  3. Ian Brabham reporter
    • removed issue_priority

    The issue was updated with the following change(s):

    • The priority has been updated, from Normal to High.
  4. Peter Urbanec
    • removed issue_category

    The issue was updated with the following change(s):

    • The category has been updated, from Not determined to Application / User Interface.
  5. Ian Brabham reporter
    • removed issue_severity

    The issue was updated with the following change(s):

    • The severity has been updated, from Normal to Major.
  6. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Confirmed to Testing.
  7. Peter Urbanec
    • removed issue_resolution
    • removed issue_percent
    • removed issue_close
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Testing to Closed.
    • This issue has been closed
    • This issue's progression has been updated to 100 percent completed.
    • The resolution has been updated, from Not determined to Fixed.
  8. Log in to comment