Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Incomplete
-
Affects Version/s: 2.11.2, 2.11.2.0
-
Fix Version/s: 2.11.2.0
-
Component/s: Properties and Preferences, Structures
-
Labels:None
Description
[ see comments for latest status on this issue] In the java 11 file chooser, it is not possible to drill down within an application's directory, so as a user testing ChimeraX rc builds I simply picked ChimeraX-1.0rc2020xxx.app when testing JAL-2422 rather than providing the full path to the MacOS/chimeraX executable within the app's directory.
Jalview helpfully decided to instead use a default search path to locate ChimeraX without warning me that the configured path was not usable.. I only realised this when an old version of ChimeraX was launched, but should have instead been warned that the path was not usable when I set it in preferences.
First need to check if this happens in Jalview 2.11.1 for Chimera. If it doesn't then tag this bug as 'indevelop' !
Jalview helpfully decided to instead use a default search path to locate ChimeraX without warning me that the configured path was not usable.. I only realised this when an old version of ChimeraX was launched, but should have instead been warned that the path was not usable when I set it in preferences.
First need to check if this happens in Jalview 2.11.1 for Chimera. If it doesn't then tag this bug as 'indevelop' !