- removed issue_reproducability
- removed issue_update
- removed issue_status
Seekbar Broken in TV mode
Issue #195
resolved
In TV mode the activation of the seek bar does not work.
The seekbar should be activated by a long press of the navigation Left or Right buttons.
Reproduction steps
Long press of the Left or Right Navigation buttons does not bring up the "seekbar"
Comments (6)
-
-
- removed issue_reproducability
- removed issue_update
- removed issue_status
From the Help menu "Seek forward (enter time)" and "Seek backward (enter time)" identify a Long Press of the Right and Left arrows respectively and when actioned correctly bring up the seekbar.
-
IanB wrote:
From the Help menu "Seek forward (enter time)" and "Seek backward (enter time)" identify a Long Press of the Right and Left arrows respectively and when actioned correctly bring up the seekbar.
When the seekbar is entered this way in LiveTV, it shows a huge number for the "seek position" at the bottom left of the seekbar. This number changes when the LEFT/RIGHT button moves the seek position, but when OK is pressed, nothing happens: the T3 stays in LiveTV mode. If the seekbar is displayed in LiveTV mode, it should display sensible data, and actually perform a function. Otherwise it should not be displayed.
If the T3 is in timeshift mode, the seekbar appears to operate correctly.
-
- removed issue_category
The issue was updated with the following change(s):
- The category has been updated, from Not determined to Application / User Interface.
-
In the code, the seek bar is not intended to be available in either live TV or while timeshifting. The appearance that it was available has the same cause as other problems mentioned in bug 301.
The seek bar activation is now only mentioned in the help while playing recordings, and it does activate the seek bar.
The keymap for context InfobarSeekActionsPTS in keymap.xml does not have entries for seekFwdManual or seekBackManual, even though the ActionMap that uses this context in InfoBarGenerics.py has action mappings for those two action names.
Perhaps this bug should be marked as resolved, and a new, more specific bug opened to enable this action while timeshifting.
-
- 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 Confirmed 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.
- Log in to comment
The issue was updated with the following change(s):