Brightness/Contrast: default button is required but unset about imagej2 HOT 1 CLOSED

Thanks for reporting this @hinerm, it cracked me up.

The issue is that for buttons in an input harvester dialog, we currently have a big hack where each button is declared as an "input". And then I added logic (finally, long after I should have) to perform a final validation that required parameters are indeed set. The thing with buttons is that their "value" is never set, because they aren't really real.

There are workarounds, like setting each button parameter to required=false or to a different visibility maybe, but really the Button should probably extend a marker interface that indicates to the module framework that the parameter should be considered special in some manner.

I'll fix it later this week or next, as time allows.

from imagej2.