*NO BUG* Insert/Delete row

[Mat]

First to mention; thanks for yet another lovely update! Nerdseq brings so much joy

One thing though, I can not quite seem to get the hang yet of the "Insert Row" function. In pattern-screen it works just fine. Both deleting and inserting a row. When in sequencer-screen though, it doesn't same to work. Only deleting (shift+up+delete) works, but only for the current column, not for the entire row. Inserting (shift+down+delete) doesn't seem to do anything.

[XORadmin]

Thats correct. This is only implemented in the pattern screen.
Not sure if i will add it to the sequencer screen.

[Mat]

Thats correct. This is only implemented in the pattern screen.
Not sure if i will add it to the sequencer screen.

Cool! Thanks

[MATTHS]

Please please Please please Please please Please please Please please Please please Please please Please please Please please Please please Please please Please please add this to the Sequencer screen! ??

[XORadmin]

Actually, this creates an issue. Having the shortcut (and there is only one shortcut for both up and down possible).

It would be either one column only or the whole row only.
And you can do both using the functions with Mark.

So yes, what is prefered? Remove the column and go full for the row or the other way around?

[MATTHS]

I think being able to move the whole row would be best because it is highly probable that you have a row of patterns that are working well.

Thanks and hope this can be implemented!

[XORadmin]

I think being able to move the whole row would be best because it is highly probable that you have a row of patterns that are working well.

Thanks and hope this can be implemented!

That is actually a reason for you. I would more think of: Then it is the same as with the pattern screen.
But on the other hand, SHIFT+UP+DELETE shifts only one column up right now. This should then also be for the whole row.
With pattern screens it makes sense to shift whole rows since a row got mostly functions which are related to each other. But that is different with the sequencer screen and totally depends on your favourite workflow.

I will skip this for this release now. You can do the same functions with the mark functions anyway, so it is not a too big problem to wait for the perfect implementation I think :-)