For triggers that support listing multiple conditions at once, TriggerList splits them into several "references". E.g. a trigger to listen on ports "1200,1300" will be present as two lines:
Listen on 1200
Listen on 1300
When you right-click and delete one of these lines, both disappear because it's actually the entire trigger that gets deleted.
This is counter intuitive. Instead only that reference should be removed from that trigger. E.g., deleting "Listen on 1300" should edit the trigger to make it listen on ports "1200".
The change is not straightforward as there needs to be some decision process on how to delete each line. When doing multi-deletion there also probably needs to be some sorting/grouping so that we don't edit the same trigger twice. But the latter may be optional.
Original report by me.
For triggers that support listing multiple conditions at once, TriggerList splits them into several "references". E.g. a trigger to listen on ports "1200,1300" will be present as two lines:
When you right-click and delete one of these lines, both disappear because it's actually the entire trigger that gets deleted.
This is counter intuitive. Instead only that reference should be removed from that trigger. E.g., deleting "Listen on 1300" should edit the trigger to make it listen on ports "1200".
The change is not straightforward as there needs to be some decision process on how to delete each line. When doing multi-deletion there also probably needs to be some sorting/grouping so that we don't edit the same trigger twice. But the latter may be optional.