Changes between Initial Version and Version 1 of Ticket #13003, comment 2


Ignore:
Timestamp:
Feb 27, 2017, 7:21:42 AM (7 years ago)
Author:
stuartm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13003, comment 2

    initial v1  
    11This tends to happen when the program times don't quite add up. There's some logic in there to try and deal with this but it's not completely robust. I actually thought this was solved long before 0.28 was released, but it seems to have made a reappearance, either because of WebFrontend changes (unaware of any post-0.28) or because the newer guide data is triggering a cause of the bug which wasn't handled.
    22
    3 Technical: Each 'program' is a <div> with a css width. The width is calculated based on the displayed time frame - 120 minutes divided by the program length within that timeslot. e.g. a 60 minute program is given a width of 50%. However due to rounding issues or overlaps between two back to back programs, sometimes the total width for the divs is greater than 100% (e.g. 101%) and when this happens, the program wraps to the next line (channel) in the grid where it's then hidden behind other divs/programs.
     3Technical: Each 'program' is a <div> with a css width. The width is calculated based on the displayed time frame - 120 minutes divided by the program length within that timeslot. e.g. a 60 minute program is given a width of 50%. However due to rounding issues or overlaps between two back to back programs, sometimes the total width for the divs is greater than 100% (e.g. 101%) and when this happens, the last program wraps to the next line (channel) in the grid where it's then hidden behind other divs/programs.