Vali-98
commented
1 month ago Actually the current implementation does use a , seperator for multiple stop sequences which admittedly is pretty poor implementation. I will look into proper multistop sequences.
The UI for this feature isn't exactly difficult, its more about managing the database entry and migrating it to a new system without breaking installs.
Some models have officially multiple stop sequences. Or sometimes you need multiple stop sequences for different reasons. I think the easiest way would be a + button which adds a new text box for stop sequence 2 and so on. I wouldn't separate multiple stop sequences with a "," or something, that would be too complex as you would also need to be able to escape that and so on.