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

Mastodon Collaborative - Don't require restart after cloning a shared project #7

Open
maarzt opened this issue Nov 6, 2023 · 0 comments

Comments

@maarzt
Copy link
Collaborator

maarzt commented Nov 6, 2023

User story

After cloning a shared project, the BDV XML/HDF5 will often be in a wrong location, and the user will need to fix the respective path. This requires the user to find the correct menu and restart Mastodon.

Solution

  1. Mastodon already shows a dialog that allows the user to open dummy image data or to cancel. This dialog should could offer a third option to fix the image path.
  2. Another solution would be to offer to restart mastodon after showing the already existing fix image path dialog.
  3. It would be great if we could add the newly cloned project to the list of recently opened projects.
@maarzt maarzt transferred this issue from mastodon-sc/mastodon-tomancak Mar 12, 2024
@stefanhahmann stefanhahmann changed the title Mastodon Collaborative - Don't require restart after cloning a share project Mastodon Collaborative - Don't require restart after cloning a shared project Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant