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.

Bug 850 - multiple instances of FIJI
multiple instances of FIJI
Status: RESOLVED WONTFIX
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Windows
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2014-07-10 12:12 CDT by raymundyin
Modified: 2014-07-22 16:46 CDT
3 users (show)

See Also:

Description raymundyin 2014-07-10 12:12:08 CDT
Hi, thanks for the help in the chat room

My problem is that for each .tif file I open, FIJI will create a new instance of the toolbar.
I set the ImageJ-win64.exe as the default program to open .tif files 
When I first open an image it will launch FIJI - all gravy and now FIJI is open
but if i were to open another image, it will launch  FIJI again so I have two iinstances of the program and so that I have 4 windows (FIJI toolbar, image1, FIJI toolbar, image2).

Ideally, and what it has done in the past is: opening the first image launches FIJI but opening a second image will not launch FIJI but instead will open the image under the same, first instance of FIJI so that the two images can be associated (stacked or merged or whatever)

I can manually drag and drop the files into the FIJI toolbar to force the two images to be in the same instance of FIJI. 

The other thing is if I open a particular image twice, it will distinguish the two by appending a -01 to the file name and will continue counting for each additional duplicate. I am finding that it will continue counting even if no images are open. Meaning that if I were to open "photo1.tif" and then open it again, it will be named "photo1.tif-1". However if I were to close both these windows so that only the FIJI toolbar remains, and were to then reopen "photo1.tif" the naming would be "photo1.tif-2". It seems to still think that there are duplicates open.

I wonder if I am using the wrong launcher or something

Thanks again for the help, I hope it was clear enough

-Ray

Information about your version of Java:

  os.arch => amd64
  os.name => Windows 7
  os.version => 6.1
  java.version => 1.6.0_24
  java.vendor => Sun Microsystems Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_24-b07
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 19.1-b02
  java.vm.vendor => Sun Microsystems Inc.
  java.vm.info => mixed mode
  java.awt.graphicsenv => sun.awt.Win32GraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.6
  sun.cpu.endian => little
  sun.desktop => windows
  file.separator => \

The up-to-date check says: REMIND_LATER

Information relevant to JAVA_HOME related problems:

  JAVA_HOME is set to: C:\Fiji.app/java/win64/jdk1.6.0_24//jre
  imagej.dir => C:\Fiji.app

Information about the version of each plugin:

Activated update sites:
ImageJ: http://update.imagej.net/ (last check:20140702164308)
Fiji: http://fiji.sc/update/ (last check:20140707044211)
Comment 1 Johannes Schindelin 2014-07-22 15:23:02 CDT
In contrast to ImageJ 1.x, ImageJ2 does not have the single-instance listener.
But you can open multiple images at the same time in which case the same instance will open them all.

As to the suffix: this is intentional, as ImageJ 1.x' macro language frequently identifies the current image *by name*.
Comment 2 Curtis Rueden 2014-07-22 15:41:02 CDT
The fact that a numerical suffix is still used after all images are closed, is a bug, though. Probably the same bug as: http://fiji.sc/bugzilla/﷒0﷓

Johannes, are you sure we don't want to support the single instance feature in some way? I think it is useful to a lot of people. We could file a GitHub issue for it...
Comment 3 Johannes Schindelin 2014-07-22 16:46:01 CDT
> The fact that a numerical suffix is still used after all images are closed, is a bug, though.

Oh yeah, and yes, I agree this is probably the same as #774.

> Johannes, are you sure we don't want to support the single instance feature in some way?

Hmm. I hoped that I could concentrate on other tasks. But if you think that this feature (which BTW caused also problems in the past, it was not flawless a feature by design, just think of Fiji not opening when you launch it a second time because there is already an instance), sure, why not open a GitHub issue.