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

Differentiate between initially dynamic and iteratively dynamic modules #180

Open
ctrueden opened this issue Aug 21, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@ctrueden
Copy link
Member

commented Aug 21, 2015

Some modules are dynamic during initialization, but once the initialize() stuff has been done, parameters are fixed.

Other modules want to be dynamic during callbacks (i.e., changes to parameter values), which makes things more challenging. In particular, such dynamic changes are not reflected in the input harvester UI currently, because the UI is only built once, and not rebuilt when callbacks occur.

It would be nice to have a more powerful UI that supported iteratively dynamic modules. And it would be nice to be able to tell the difference between these two sorts of modules in a programmatic way—e.g., if they extended different abstract base classes.

See also this thread on imagej-devel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.