You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really useful if when display options are provided at the command line before any image files, they are applied to all following images, rather than having to set display options for each image.
For example:
fsleyes -cm -dr 0 10 /path/to/images/*.nii.gz
The text was updated successfully, but these errors were encountered:
I think this would be too complicated to implement within the existing argument parsing logic. However, it would be very straightforward to implement it as a separate entry point (i.e. a second command called e.g. fsleyes_all [just a placeholder] in addition to the standard fsleyes). Alternatively it be invoked via a global argument, e.g. fsleyes --all [other arguments], which could be checked for and used to invoke a separate entry point which re-arranges the arguments and pass them to the main argument parsing routines.
But in either case this separate entry point would have to be somewhat limited, i.e. you wouldn't be able to pass other global options (e.g. -std, --scene lightbox, etc). Unless, for example, the user were to pass a delimiter separating the global from the overlay arguments, e.g. (OVERLAY_ARGS being a placeholder for the delimiter):
Thanks for your reply. I think either of your suggestions would provide the right functionality, and I'll defer to your judgement about how this could be incorporated with the argument parsing logic. The thought simply came to me the other day when I was mass-loading multiple images that I know ahead of time to all be on the same data scale.
It would be really useful if when display options are provided at the command line before any image files, they are applied to all following images, rather than having to set display options for each image.
For example:
fsleyes -cm -dr 0 10 /path/to/images/*.nii.gz
The text was updated successfully, but these errors were encountered: