|
Bugzilla – Bug 685 |
Weird Stitching UI behavior. |
Last modified: 2014-01-08 12:20:09 CST |
| ⚠ |
NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug. The Fiji project now uses GitHub Issues for issue tracking. Please file all new issues there. |
|
|
|
||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||
The stitching UI behaves very weird after being started by a macro command *once*. Steps to reproduce (tested on Linux and Win7 x64): * download a fresh copy of Fiji * start * run the stitcher via Plugins > Stitching > Grid/Collection stitching * "normal" dialog comes up (notice the graphic representation of the selected settings) * hit "Cancel" * File > New > Script * Language > ImageJ Macro * enter 'run("Grid/Collection stitching");' * hit "Run" * dialog doesn't show the graphical representation, *AND* allows for invalid combinations of options (e.g. "Positions from file" and "Right & Down") I could live with the temporary workaround of not calling the stitcher from a macro for a while, however after starting it using the above described command *once*, the behavior stays like this. I.e. you can't run it correctly from the Plugins menu anymore either. Cheers ~NikoStephan, You could try using IJ.macroRunning() instead of IJ.isMacro(). Here is the source for these two methods: /** Returns true if the run(), open() or newImage() method is executing. */ public static boolean macroRunning() { return macroRunning; } /** Returns true if a macro is running, or if the run(), open() or newImage() method is executing. */ public static boolean isMacro() { return macroRunning || Interpreter.getInstance()!=null; }