Hi, I would like to report a bug that seems to have been introduced in version 3.1.0
The bug, which I will now explain in detail, was present in at least version 3.1.0 and the latest 3.1.2 on a Windows 10 computer (Not tested on other OSs).
Versions 3.0.2 and 3.0.5 instead work correctly (Both on Windows 10 and Ubuntu 20.04).
Issue
The issue is with the cursor NOT snapping to the position of a single-point label when clicking on its textbox.
Details
The snapping behavior was present in at least version 3.0.2 and 3.0.5, and it is crucial for precise alignment of the position of labels.
I used to be able to click on the text of a point label (not region) and have the cursor automatically align with the position of the label.
Then I would move around the label and the cursor moved along with the label itself, which helped to align it to events in the audio signal.
Now I can still click on the textbox of a label (and edit the text) but the cursor remains where it is.
Moving the label results in having no precise idea of where it is with respect to the signal on other tracks.
Attachments
The following attachments show how, in the newer version, the textbox of the label is selected but the cursor is still somewhere else.
Please, disregard the fact that on these screenshots the cursor is always at the beginning of some activity in the signal: my point is that the cursor used to be automatically aligned with the actual position of the label, which in the first case (working) corresponds also to the beginning of a note in the signal, while in the second (not working) it corresponds to few ms before.
Working function (v3.0.2, Windows 10):
Not working (v3.1.0, Windows 10):
I hope this can be fixed in the next release, it is really useful for onset labeling on music datasets
Have a nice day.