-
Notifications
You must be signed in to change notification settings - Fork 18
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
Allow more flexible image input options #71
Comments
I would like to weight in here! For using commands both from within the GUI and headless ("write once run everywhere") I would find it almost essential to have the |
...for the headless use-case: would it also be possible that the Context realizes that the Command is called headless, thus knows that images cannot come from the GUI, and thus any Image parameter automatically would also take filepaths as a input? |
@tischi wrote:
I think it wouldn't even be necessary to detect we're running headless. The presence of a The question is whether having such converters (from |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/new-colocalization-cross-correlation-plugin-looking-for-feedback/49492/2 |
Currently, module inputs of type
Img
(andImagePlus
,Dataset
, etc. via converters) are handled byObjectWidget
andSwingObjectWidget
that offer a simpleJComboBox
with a list of convertible objects.It would be nice to offer more flexibility via a
style
attribute, to allow:style="file"
)style="file-or-image"
)Another (maybe more elegant) option would be to create a singleton object that shows up as "Load from file..." option in any dropdown list for image inputs, thereby allowing to choose an open image or load from file at will.
See saalfeldlab/bigwarp#42 (comment) for the discussion that triggered this issue.
The text was updated successfully, but these errors were encountered: