Posted by
CARL Philippe (LBP) on
Jul 30, 2020; 11:53am
URL: http://imagej.273.s1.nabble.com/Weird-behavior-with-GenericDialog-addImage-tp5023785p5023789.html
Hi again Gabriel,
I agree that the issue you are describing may indeed arise in the case you are compiling a code "outside" ImageJ (and then want to run it inside).
But not when using the Plugins>Compile_and_run... tool directly within ImageJ (which is the way I always work).
And if so, this would really be the first time I see such a "memory behavior" (unless of course there is already another compiled version within the plugins folder or one of its subfolder which isn't the case here).
Take care,
Philippe
----- Mail original -----
De: "Gabriel Landini" <
[hidden email]>
À: "imagej" <
[hidden email]>
Envoyé: Jeudi 30 Juillet 2020 13:35:33
Objet: Re: Weird behavior with GenericDialog.addImage
On Thursday, 30 July 2020 11:39:42 BST you wrote:
> Thanks a lot for your replay, nevertheless I'm not really sure what you want
> to point me out here.
Hi, what I said before: once we compile a plugin, we should "refresh menus"
or restart IJ otherwise if you use the menus to call a recently compiled file,
the old version might still remain on memory and that would run instead of the
recently compiled sitting on disk.
Isn't this what you reported?: a newly compiled plugin "remembering" an image
size of the old version?
If I misunderstood the problem, sorry, just ignore this.
Regards
Gabriel
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html