-
Notifications
You must be signed in to change notification settings - Fork 23
Add auto-save option #1580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add auto-save option #1580
Conversation
Adds a new setting to automatically save annotation changes after a 2-second debounce delay. The feature batches rapid edits to reduce server requests and respects readonly mode. Disabled by default for backward compatibility. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add auto-save toggle to desktop Settings view under Annotation Settings - Add Annotation Settings section to web-girder Settings view with multi-camera toolbar and auto-save toggles - Change save icon to show gear (mdi-content-save-cog) when auto-save is enabled to visually indicate automated saving is active Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The save() function was unconditionally exiting editing mode before saving, which caused issues when auto-save was enabled: users would be kicked out of polygon/segmentation editing mode after 2 seconds when auto-save triggered. Added an optional exitEditingMode parameter (defaults to false) so auto-save no longer disrupts the user's editing session. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
naglepuff
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of small bits of feedback, but mostly looks good
| <v-row> | ||
| <v-col> | ||
| <v-switch | ||
| v-model="clientSettings.multiCamSettings.showToolbar" | ||
| color="primary" | ||
| label="Show multi-camera toolbar" | ||
| hint="Show multi-camera editing tools in the top toolbar when a track is selected" | ||
| persistent-hint | ||
| class="my-0" | ||
| /> | ||
| </v-col> | ||
| </v-row> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this isn't related to auto-save, and we don't yet support stereo/multi camera in web, should we remove this for now?
| async () => { | ||
| if (readonlyState.value) return; | ||
| if (pendingSaveCount.value === 0) return; | ||
| if (saveInProgress.value) return; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if a user makes a change while a save is happening? I assume that this debounced function will be scheduled, but may end up returning early if a previous save is still in progress.
Should we also be watching saveInProgress, and check to see if we need to retry the save after the value changes from true to false?
Body:
Summary
mdi-content-save-cog) when auto-save is enabled to visually indicate automated saving is activeTest plan
The branch contains 2 commits: