search

jsbroks / coco-annotator

:pencil2: Web-based image segmentation tool for object detection, localization, and keypoints
MIT License
2.11k stars 460 forks source link

Keyboard shortcuts not working #605

Open wenbo0117 opened 1 year ago

wenbo0117 commented 1 year ago

After setting up the shortcut key, when I move to the next image, the shortcut key is refreshed

SixK commented 1 year ago

reproduced here too using vue3. new shortcut keys are saved when clicking save button, read when refreshing page, but if you change image, you loose custom shortcuts.

I guess the code doesn't use saved values, but shortcut default values. Well, coco-annotator is only v0.11.1 ! I would say, the function is not implemented.

If you are really sure of the shorcuts you want, modify this file : https://github.com/jsbroks/coco-annotator/blob/master/client/src/mixins/shortcuts.js And rebuild you docker image (docker-compose -f docker-compose.yml build)

wenbo0117 commented 1 year ago

edited coco-annotator\client\src\mixins\shortcuts.js

PS E:\coco-annotator> docker-compose -f docker-compose.yml build [+] Building 0.0s (0/0)

Then open it as before

a little trouble，I am windows, or is there a way to lower the version.Please tell me the process and order.At the same time, I don't know how to uninstall. I feel that there is still a problem with uninstalling and reinstalling before.

wenbo0117 commented 1 year ago

How do I download an old version? I downloaded the compressed file of an old version, tried to cd into coco-annotator, and ran docker-compose up. After running it, it still shows version 0.11.

SixK commented 1 year ago

Well, there is no uninstall/reinstall mechanism. Here we use docker that is a virtual machine. With docker-compose you build and start images in docker. You can find a pre-built docker image here if you really break everything and you don't find how to build again: https://hub.docker.com/r/jsbroks/coco-annotator

If you want to build an older version, you can clone github project, then checkout the tag you want with git. And then run docker-compose -f docker-compose.yml build (or any other docker-compose file present at project roo (dev, gpu) But why would you want an older version ? When doing modification on source code, version number don't change. In a doubt, you can also add --no-cache parameter to force docker-compose to rebuild everything.