Skip to content
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

[Feature Request] Swate save --> save ARC button #302

Closed
Brilator opened this issue Nov 19, 2024 · 3 comments
Closed

[Feature Request] Swate save --> save ARC button #302

Brilator opened this issue Nov 19, 2024 · 3 comments
Assignees
Labels
Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature

Comments

@Brilator
Copy link
Member

After some swate performance improvements, users now have to click "save" twice when interacting with Swate view / Annotation tables:

  1. Click on Save inside swate (top-left)
  2. Click in Save ARC in sidebar

I'd suggest to have 1. trigger 2.
To my understanding this would make the sidebar button obsolete.

@github-actions github-actions bot added the Status: Needs Triage This item is up for investigation. label Nov 19, 2024
@JonasLukasczyk JonasLukasczyk self-assigned this Nov 19, 2024
@JonasLukasczyk JonasLukasczyk added Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature and removed Status: Needs Triage This item is up for investigation. labels Nov 19, 2024
@JonasLukasczyk
Copy link
Collaborator

Having two buttons is really unnecessary. I know the second button was introduced to cope with a performance issue in SWATE which prohibited realtime serialization of the modified ARCs. So users now have to manually trigger this "long" save process. In fact this is a bigger design problem now. Previously, users edited Investigations/Studies/Assays and then the modified versions were immediately send back to ARCitect which then stored them to disk only after users pressed the save button. So the only way to lose work was to make changes with SWATE and then close ARCitect before pressing the save button. Now there are even two ways users can lose work.

What about this solution:

  • we remove the save button from ARCitect
  • when the save button in SWATE is pressed then ARCitect also saves the ARC to disk
  • if users click on another I/S/A file in ARCitect while they have unsaved changes in SWATE they should see a confirmation dialog warning them that they could lose work

For the last part @Freymaurer and I will at least have to communicate a 'modified' flag between ARCitect and SWATE.

@Freymaurer
Copy link
Collaborator

I also thought about your second suggestion which should feel the most natural. Maybe both save Buttons should save current progress in Swate to disc. But having the ARCitect button do this will require a new communication path.

As this is only a temporäre fix, i suggest going for the second option for now. Save button in swate should also save to disc. Anything else will be done after evaluation.

@JonasLukasczyk
Copy link
Collaborator

now a SWATE save will trigger an ARCitect save. Since there is no need to manually save an ARC without SWATE I removed the save button from ARCitect. In the future the user should get a warning if changes were made that would be lost when the user changes to a different I/S/A file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature
Projects
Status: Done
Development

No branches or pull requests

3 participants