Posted by
Michael Schmid on
Feb 14, 2018; 1:34pm
URL: http://imagej.273.s1.nabble.com/grid-setConstraints-issue-with-Choice-tp5020048p5020091.html
Hi Philippe,
do you need the DialogListener interface for preview?
If not, you can remove all the DialogListener stuff (e.g. use sparate
listeners) or create your own DialogListenerExt interface.
If you want preview, I see no nice solution.
Preview is done by the combination of the PlugInFilter implementing the
DialogListener, the GenericDialog, and the PlugInFilterRunner, you can
have it only with a GenericDialog.
In that case, we have to ask Wayne whether he would agree to have a
modification of the GenericDialog to have more that one item per line.
Maybe this is something that others might also like?
I had already a few cases where I would have liked to have a number and
a checkbox in one line, e.g. for keeping some parameters fixed in
optimization/curve fitting, or several pairs of numbers (ranges).
[For some applications like this, there would another small problem:
In many cases, the second item in the line would not have a unique
label, e.g. for fixing some parameters, there would be several
checkboxes with 'fix', or for several ranges, there would be just a 'to'
between the numbers. Then it would not be macro-recordable.]
Best,
Michael
________________________________________________________________
On 14/02/2018 13:41, Philippe CARL wrote:
> Hi Michael,
> Your suggestion was indeed correct and I was then able to compile the GenericDialogExt code after disabling 2-3 things from the code (like code referring to "((DialogListener)dialogListeners.elementAt(i)).dialogItemChanged(this, e)").
> But then when I try to compile the code that using this newly compiled class it doesn't accept that I use:
> public boolean dialogItemChanged(GenericDialogExt gd, AWTEvent e)
> but I have to overwrite the method using:
> public boolean dialogItemChanged(GenericDialog gd, AWTEvent e)
> But if I do so then there isn't any more a dialogItemChanged detection on the defined GenericDialogExt window.
> How can I solve this new issue?
> I thank you very much in advance for your help on this one.
> Philippe
>
> -----Message d'origine-----
> De : ImageJ Interest Group [mailto:
[hidden email]] De la part de Michael Schmid
> Envoyé : mardi 13 février 2018 16:02
> À :
[hidden email]
> Objet : Re: grid.setConstraints issue with Choice
>
> Hi Philippe,
>
> my guess is that the ImageJ class loader needs a constructor with no argument for Compile&Run, e.g.
> public GenericDialogExt() {
> this("");
> }
>
> Java seems to create a no-argument constructor by itself only if there is no other constructor (The GenericDialog has a constructor with a String argument).
>
>
https://stackoverflow.com/questions/3078389/why-do-we-need-a-default-no-argument-constructor-in-java#4490416>
> Michael
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html