imagej / imagej/imagej2

Do not let ImageJ settings impact macros and scripts

Open
#93 3 comments 0 reactions 1 assignee Claimed by @ctrueden View on GitHub
Dominant language
Java
Stars
1.4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Right now, the current ImageJ settings (e.g., whether Edit>Options>ImageJ2 "Use SCIFIO when opening files" is ticked) impact the behavior of macros and scripts. This can cause very difficult-to-diagnose problems, which can only be "fixed" by clearing the preferences. Further, it ruins reproducibility: write a macro and give it to a colleague and it may not work the same way on their exact same version of ImageJ!

We need to concoct a solution to this conundrum. Probably, all ImageJ commands should always take the relevant settings as parameters, but get filled from the ImageJ settings via a preprocessor. That way, recorded scripts and macros would embed the value in the recorded script, rather than assuming it from the program state next time the macro is run.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.