Cross-drive saves and one File List row per image on Windows

Your images sit on D: and the folder you save annotations into is on C:. You draw the first shapes, auto-save fires, and Labelme closes with an unexpected-error dialog — the shapes go with it. The two drives share no common starting point, so the short image path that Labelme normally writes beside the shapes has no form it can take, and the save stops there.

In v7.1.0, that save completes. When there is no short path from the annotation to the image, Labelme writes the image's full path instead — D:\datasets\site-a\img_0001.jpg rather than a path relative to the annotation file. Reopening it on the machine that saved it works as usual. What you give up is portability: an annotation written this way finds its image only as long as the image stays where it is, so copying the pair to another machine or another drive layout leaves it pointing at a path that no longer exists. Saves within one drive are untouched and keep the short, movable path. The cross-drive save fix closes issue #1350, reported from Windows 11 in November 2023 and open for close to three years.

The File List counts each image once#

Windows accepts both \ and / between folder names, and the same image spelled two ways read as two different files. Dragging an image onto the window from a folder you had also opened put it in the File List a second time. Opening an image through File → Open had the mirrored effect: its row went unselected, and the saved checkmark never appeared beside it after you saved.

Both paths now take the platform's own spelling before they reach the File List. Dropped files are normalized where they enter, and images opened through a file dialog are normalized as they load, so one image is one row — selected while you work on it, checked once it has an annotation.

The fixes ship in Labelme v7.1.0.