Alternate pattern cloning behavior

[XORadmin]

splithyfred, can you suggest which key combo you would want to claim for this function? They’re in limited supply, and functions have already been pushed to the nerd menu to avoid adding even more key combos or inconsistency in their behaviour when used in different places. Thomas’ option likely hits the sweet spot.

mvdirty, there would be no need for a key combo at all! It would be an alternate behavior that overrides the current behavior for cloning. There could be an option to toggle the behavior on or off in the setup menu. This way you could choose which cloning mode is best for your workflow. For me, the current behavior does not feel right, and for others it might be perfect.

I got to say that I think the current normal behaviour is the best in my eyes for a single pattern clone (multiple ones would be easy as well).
You clone, you get the new pattern immediately and no field around it on the sequencer screen is affected, overwritten shifted etc.
That would not be natural to have that.

What would be the impact of this special cloning behaviour, (also from the developer view)? :
All editing is as generic as possible and you know pretty everywhere how to navigate or how to change values. They are of course some exclusions, but these are also specialities where a regular editing is not enough.
For now, there is the normal editing and in a marked situation. Something that is common to all the screens. If in mark mode, you are kind of trapped until you either abort or leave the screen or do the editing. Another special mode for only one function would mean a step away from the generic usage (and that for one specific function), you are trapped then in a situation where you can only browse up/down, you still need to press multiple buttons to archieve what you want and it would need also many specials to catch all side-effects. You would need to repeat this for multiple patterns to clone. Also to mention that it would most probably not an obvious result if someone presses SHIFT+OK by accident (even if it would be another setup option, which will for sure be turned on by people without knowing the results). So the work for that would have quite an impact developerwise. It would also be different from the same functions for cloning tables or cloning patches.

I agree also that I rather add sequencing functionality than editing ones for things that can be archieved easily, even without workarounds. The Nerd Menu is in my opinion definitely the way to go for batch actions. ( Not sure what the issues are with the Nerd menu. It is easy to access and adds extra functionality one click further. In the end these are special functions and still you don't have to dive deep into submenus of submenus of submenus....luckily).


I still think my option would be the way to go ( and not because it was my idea...you know I am always happy for other views of people ). Also to do something more with cloning was not on my list at all. So it would be a low-prio thing anyway because you can do all needed already.

Let it sink a bit....