sidfactory2
sidfactory2 copied to clipboard
Ctrl+F on a table index pointer for next free spot
With the cursor on a table index pointer byte (i.e. in the commands or instruments table) hitting Ctrl+F could mirror the order list counterpart by automatically filling in the next free index value, then also place the cursor in the corresponding table (e.g. wave, pulse, filter) at that index row - ready to type in data.
This is a task migrated from workstreams in Slack.
In the Bonzai Slack workspace, @TheRealLaxity commented there that he would have to think about the implementation because it's special in relation to how the functionality is described in the driver meta data in the emulation layer.
In the Bonzai Slack workspace, @TheRealLaxity commented there that he would have to think about the implementation because it's special in relation to how the functionality is described in the driver meta data in the emulation layer.
Wouldn't you just backtrack from the end of the table to the first non-zero number, regardless of the driver? You'd have to know the number of columns (and which table it is of course).
With the cursor on a table index pointer byte (i.e. in the commands or instruments table) hitting Ctrl+F could mirror the order list counterpart by automatically filling in the next free index value, then also place the cursor in the corresponding table (e.g. wave, pulse, filter) at that index row - ready to type in data.
.. and command ditto (pointers to table from commands)
In the Bonzai Slack workspace, @TheRealLaxity commented there that he would have to think about the implementation because it's special in relation to how the functionality is described in the driver meta data in the emulation layer.
Wouldn't you just backtrack from the end of the table to the first non-zero number, regardless of the driver? You'd have to know the number of columns (and which table it is of course).
Can you explain what you mean?
In the Bonzai Slack workspace, @TheRealLaxity commented there that he would have to think about the implementation because it's special in relation to how the functionality is described in the driver meta data in the emulation layer.
Wouldn't you just backtrack from the end of the table to the first non-zero number, regardless of the driver? You'd have to know the number of columns (and which table it is of course).
Can you explain what you mean?
I read 'next free spot' as 'the end of the table', where the rest of the table is just zeroes. This is the feature I had in mind myself.
In the Bonzai Slack workspace, @TheRealLaxity commented there that he would have to think about the implementation because it's special in relation to how the functionality is described in the driver meta data in the emulation layer.
Wouldn't you just backtrack from the end of the table to the first non-zero number, regardless of the driver? You'd have to know the number of columns (and which table it is of course).
Can you explain what you mean?
I read 'next free spot' as 'the end of the table', where the rest of the table is just zeroes. This is the feature I had in mind myself.
Oh that. The functionality for finding the first free is already there. Press end on a table and it goes to the first free.