schedulerCanvasHeight is currently being computed in App and passed to CanvasPage. This is problematic for the following reasons:
- 'App
should not be aware ofAutoSizedCanvas's and renderCanvas`'s implementation details
schedulerCanvasHeight is insufficient for AutoSizedCanvas's use case. schedulerCanvasHeight is passed to both usePanAndZoom and getHoveredEvent. In Brian's design, the scheduler canvas area only contained the 4 priority rows, and this height made sense. However, in the new design with separate event row and measure lanes, getHoveredEvent needs to know the heights of the events row and the measure lanes separately, but usePanAndZoom still requires the total height.
schedulerCanvasHeight should be removed from App and replaced with another approach. Ideally, we should somehow use the definitive calculations from renderCanvas.
schedulerCanvasHeightis currently being computed inAppand passed toCanvasPage. This is problematic for the following reasons:should not be aware ofAutoSizedCanvas's andrenderCanvas`'s implementation detailsschedulerCanvasHeightis insufficient forAutoSizedCanvas's use case.schedulerCanvasHeightis passed to bothusePanAndZoomandgetHoveredEvent. In Brian's design, the scheduler canvas area only contained the 4 priority rows, and this height made sense. However, in the new design with separate event row and measure lanes,getHoveredEventneeds to know the heights of the events row and the measure lanes separately, butusePanAndZoomstill requires the total height.schedulerCanvasHeightshould be removed from App and replaced with another approach. Ideally, we should somehow use the definitive calculations fromrenderCanvas.