"Move" seems to not generate conflicts in those cases.
However, logically, now the loop conflicts appear
(I forgot to check this when testing xbuses2 !!!).
If the AuxSend is copied or moved to a position that creates a loop Qtractor will crash (not immediately, but when interacting with resources related to sends).
So the most functional solution instead of resetting the "copy" or "AuxSend moved" to "none", as it happens now, could be to make use of the "cyclicAudioBuses" function, and only in the case that the loop is generated, reset the Auxsend.
I don't think I'll be able to implement this, but I'll try.
Restart the "Copy" seems to be a solution to avoid the kind of conflicts that arose when creating or deleting buses referred to in
https://www.rncbc.org/drupal/comment/10888#comment-10888
"Move" seems to not generate conflicts in those cases.
However, logically, now the loop conflicts appear
(I forgot to check this when testing xbuses2 !!!).
If the AuxSend is copied or moved to a position that creates a loop Qtractor will crash (not immediately, but when interacting with resources related to sends).
So the most functional solution instead of resetting the "copy" or "AuxSend moved" to "none", as it happens now, could be to make use of the "cyclicAudioBuses" function, and only in the case that the loop is generated, reset the Auxsend.
I don't think I'll be able to implement this, but I'll try.