You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using v1.7.2 of higlass, I have a horizontal-multivec track along with a few other non-multivec tracks (gene annotations, horizontal-point, and chromosome tracks).
When the mouse pointer moves over a non-multivec track, the multivec track behaves as though the vertical coordinate of the mouse pointer is also on the multivec track, which enables the horizontal line of the crosshair:
What I would expect is that, when the multivec is part of the top or bottom of a view, it would only show the horizontal crosshair if the pointer is within the bounds of the multivec track.
(Likewise, if the bug is consistent between orientations, a multivec that is in the left or right portion of a view would not show the vertical crosshair, unless the pointer is within the bounds of the multivec.)
The text was updated successfully, but these errors were encountered:
Yes, but I haven't been able to update my local copy of the higlass plugin due to local changes (unrelated to the multivec track). There may have been fixes applied to the higlass.io site since I reported this bug.
When the `showMousePosition` option is set to `true` and the mouse pointer moves over a non-2d track, x and y values are published internally that can cause another 2d track to draw nonsensical vertical or horizontal lines. This test clears the relevant value so that it cannot be used to render such lines.
Using v1.7.2 of higlass, I have a
horizontal-multivec
track along with a few other non-multivec tracks (gene annotations,horizontal-point
, and chromosome tracks).When the mouse pointer moves over a non-multivec track, the multivec track behaves as though the vertical coordinate of the mouse pointer is also on the multivec track, which enables the horizontal line of the crosshair:
What I would expect is that, when the multivec is part of the top or bottom of a view, it would only show the horizontal crosshair if the pointer is within the bounds of the multivec track.
(Likewise, if the bug is consistent between orientations, a multivec that is in the left or right portion of a view would not show the vertical crosshair, unless the pointer is within the bounds of the multivec.)
The text was updated successfully, but these errors were encountered: