If there were a visual indicator, such as a highlighted strip, marking the disabled area, that would align with expected behavior, and the user could handle it in various ways: either by performing a merge beforehand, or by simply removing the excess afterward and making adjustments.
As it stands, the user cannot understand what is happening because Qtractor provides no reference to indicate it.
The initial impression is that it’s a bug.
If a user sees an area, they assume it’s available for editing, it’s as simple as that. If an area is not editable, Qtractor needs to make that clear.
Another way to avoid it being perceived as a bug would be to allow editing in that area, though I suspect that would be significantly more complex to implement.
"it's not quite or at all necessary"
It is necessary...
If there were a visual indicator, such as a highlighted strip, marking the disabled area, that would align with expected behavior, and the user could handle it in various ways: either by performing a merge beforehand, or by simply removing the excess afterward and making adjustments.
As it stands, the user cannot understand what is happening because Qtractor provides no reference to indicate it.
The initial impression is that it’s a bug.
If a user sees an area, they assume it’s available for editing, it’s as simple as that. If an area is not editable, Qtractor needs to make that clear.
Another way to avoid it being perceived as a bug would be to allow editing in that area, though I suspect that would be significantly more complex to implement.