Is your feature request related to a problem? Please describe.
The baseline STROOP implementation for floors and ceilings behaves differently (and more conveniently so) than the refactor regarding min/max cutoffs and unit hovering (i.e. "copy cursor position" is continuous rather than respecting unit truncation)
Describe the solution you'd like
The conveniences from the baseline STROOP should all be present in the refactor, too.
Specifically:
set min height/set max height should crop the units that are below/above a certain height- hovering over floor units should show the respective cursor coordinate, unit truncated (what about the
show triangle units toggle, though?)
Describe alternatives you've considered
Using baseline STROOP alongside the refactor - some people do this, so it's apparently somehwat viable, but given that the whole point is convenience, it can't be the ultimate solution.
Additional context
The implementation of the triangle trackers differs severly between baseline STROOP and this refactor.
The resolution to this issue is most likely going to consist of at least three different features that are orthogonal to each other, each of which will hopefully bring more improvements outside of the scope of this issue with it.
Is your feature request related to a problem? Please describe.
The baseline STROOP implementation for floors and ceilings behaves differently (and more conveniently so) than the refactor regarding min/max cutoffs and unit hovering (i.e. "copy cursor position" is continuous rather than respecting unit truncation)
Describe the solution you'd like
The conveniences from the baseline STROOP should all be present in the refactor, too.
Specifically:
set min height/set max heightshould crop the units that are below/above a certain heightshow triangle unitstoggle, though?)Describe alternatives you've considered
Using baseline STROOP alongside the refactor - some people do this, so it's apparently somehwat viable, but given that the whole point is convenience, it can't be the ultimate solution.
Additional context
The implementation of the triangle trackers differs severly between baseline STROOP and this refactor.
The resolution to this issue is most likely going to consist of at least three different features that are orthogonal to each other, each of which will hopefully bring more improvements outside of the scope of this issue with it.