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
Dragging the lower bound up past the upper bound pushes the upper bound higher (reasonable behavior) but dragging the higher bound instead stops at the lower bound (also reasonable behavior). These are both fine but we should pick one and make it be inconsistent for both.
pushing.the.range.bounds.mp4
The text was updated successfully, but these errors were encountered:
This assymetry is actually intentional. When you have one absolute bound and one relative bound, and then move the time cursor, the bounds often collide (if the relative one follows the cursor into the absolute one). I had to decide which one would win to avoid weird fighting behaviours.
It might be slightly tricky to have this behaviour depends on the type of user interaction, as I need to set the bounds for both boundaries before I know of the interaction (typical immediate mode stuff), but there is surely a way to do it if we feel strongly about it.
Dragging the lower bound up past the upper bound pushes the upper bound higher (reasonable behavior) but dragging the higher bound instead stops at the lower bound (also reasonable behavior). These are both fine but we should pick one and make it be inconsistent for both.
pushing.the.range.bounds.mp4
The text was updated successfully, but these errors were encountered: