Hi Johannes,
Thanks for your prompt reply,
I tried moving the tool to an external directory and it didn't work; I also tried creating a new tool outside the Fiji directory and that didn't work either. What ended up working for me was clicking on the '>>' button on the fiji toolbar, resetting the toolbar to 'startup macros' and clicking 'Run' on my code again. This seems to reflect the changes that I have made. Please let me know if you have any suggestions as to how I should go about this resetting instead if there is another more optimal way
Thanks again,
Aprameya
On May 5, 2014, at 1:55 PM, Johannes Schindelin <
[hidden email]> wrote:
> Hi Aprameya,
>
> On Mon, 5 May 2014, Aprameya Mysore wrote:
>
>> I am writing a class which extends AbstractTool with the ImageJ script
>> editor. I am looking for a way to have ImageJ update my tool to reflect
>> the changes in my code when I compile it. Currently when I hit run my
>> tool does not update. I would appreciate any assistance.
>
> For technical reasons, there is a bug at the moment where newly-compiled
> code is not run, but instead old code, when the sources are stored
> in plugins/.
>
> Could you try after moving (not copying) the sources outside of the
> plugins/ folder?
>
> Ciao,
> Johannes
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html
Locked
