Rich Tabor
Rich Tabor
> We could rename it to something like RangeInputControl, a self explanatory. Maybe, let's consider that for a follow-up though.
Why not just set the minimum value of the RangeControl to 50, which is what it is effectively in trunk? That would be 1:1 to supporting today's experience with the...
Is there any way forward on this effort, or should we close this?
Yea, I don't think we need both shuffle and this change design (maybe change layout) control.
> A note on the current shuffle feature: to my understanding, isn't a real 'shuffle'. It mainly picks up the next pattern in the same category and when it reaches...
> . As such they need a title and a description to provide (in a succint way) information on their basic appearance and purpose. In the same fashion as the...
> It's worth noting that we have other similar patterns lists Yes, we can consolidate a bit. I think we should land on one toolbar implementation (this) and one inspector...
I'd hold off on this while the Assembler is sorted as a viable part of the flow or not.
Related, what do you think about shuffle being a tool only available when zoomed out? That way the intent is much clearer as a pattern-level editing tool?
> Related, I'm not a huge fan of the term "zoom out" mode since it's far more specific than simply zooming out. I wonder if something like a "Compose" mode...