Hey,
I’m running into some odd behavior with sequence (parameter block) custom parameters on cloned COMPs, and I’m wondering if this is expected. They don’t shrink when removing them from master tho.
I quickly revive this as i have no answer, I still think this is an issue that can be quite annoying if not breaking when developing on a master that is already cloned everywhere in a project.
Do you mean they don’t shrink when removing from clone?
In your video it seems shrinking the master shrinks the clone.
In this version of clones they’re intended to remain the same length as the master.
If you make changes to the clone size they could revert to the master size when re-initializing etc.
However we are looking into ways of making each clone have a unique number of blocks reliably.
What’s your ideal use case?
Thanks,
Rob.
Hey Rob, I am also running into this issue.
For my cloned components with sequence parameters, I am for example listing named colors and positions to be converted into a ramp table, or listing which window goes to which display. The UX of sequence parameters implies that this is for lists of dynamic length.
If you’re going to keep the block length of clones tied to a master (which I think hampers the usability greatly), why is the +/- not disabled to communicate that? Why allow that “glitch” of the block count deviating on the clone then popping back when the original is changed.
This currently means clones with sequence parameters need to be uncloned to be reliable.
Hi. We’re looking into this issue and testing some solutions currently.
1 Like