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

How to save as variable file formats #5

Open
liaprins-czi opened this issue Oct 12, 2020 · 3 comments
Open

How to save as variable file formats #5

liaprins-czi opened this issue Oct 12, 2020 · 3 comments

Comments

@liaprins-czi
Copy link
Contributor

liaprins-czi commented Oct 12, 2020

No instructions for saving files; no UI feedback for saving them as anything but .tiffs.


Recommendation

Consider creating a tutorial for how to save images.

This may be a Mac issue, but user should be able to save in multiple formats using menu dropdown.

Minor issue
◆◆◆ High content writing work
○○○ No design work
▽▽▽ No development work

Relates to #31

Current view when try to save file in app:
savefiletypes

@Czaki
Copy link

Czaki commented Oct 14, 2020

This is problem with design of io plugins in `napari.
Current pipeline is:

  • user provide file name
  • ask plugins in given order if it can save file with such path (suggestion is to do it base on extension)
  • if plugin accept this path then it is used to save file.

So currently there is no information about file extension from saving method.
I discus a little about this with @jni on Zulip but only about reading with consensus that reordering plugins allow to select method.

Because of this I suggest to change design work and development work to high.

Against class smell.

@liaprins-czi
Copy link
Contributor Author

liaprins-czi commented Oct 14, 2020

Thank you for the information @Czaki , I think the estimate for the engineering work would apply to #31 ; this particular issue is about the documentation, which we can update to better explain to the user how to save.

@psobolewskiPhD
Copy link
Member

Looks like this was largely fixed by napari/napari#2650

but now it's sort of broken again:
image

I agree this is something that should be more intuitive!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants