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 781 - File opener provides no way to quickly navigate to parent directory
File opener provides no way to quickly navigate to parent directory
Status: RESOLVED DUPLICATE of bug 780
Product: Fiji
Classification: Unclassified
Component: ImageJ2
unspecified
PC Windows
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2014-06-12 11:17 CDT by Rob Baer
Modified: 2014-06-12 17:28 CDT
2 users (show)

See Also:

Description Rob Baer 2014-06-12 11:17:34 CDT
There seems to be no icon for quickly getting to the parent directory.  In structured image storage this fuctionality is extremely beneficial.

Currently it seems it can only be accomplished by the file dropdown field .

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: UP_TO_DATE

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:20140611123802)
Fiji: http://fiji.sc/update/ (last check:20140610170938)
Comment 1 Curtis Rueden 2014-06-12 17:28:27 CDT
I'm going to close this in favor of bug #780, since both bugs have the same underlying cause. See that bug for further discussion and progress. Thanks!

*** This bug has been marked as a duplicate of bug 780 ***