Details
Critical Description
See JAL-3909.
If Jalview is installed in a folder that's not writable to the user, getdown refuses to continue if it cannot write a lock file before trying to update.
If there is no network, getdown is sensible enough to carry on launching without performing an update. This should be the behaviour if the Jalview install folder is not writable.
Note that the launcher.log will have to be written elsewhere (e.g. %APPDATALOCAL%\Jalview).
1) Enable getdown launch when getdown dir is not readable.
Other improvements:
2) Synchronize jalview.bin.* (in particular HiDPISetting)
3) Enable holding down SHIFT key at startup to revert to the "install/getdown.txt"
4) Attempt to set the HiDPISetting property immediately at startup (this might not work anyway and would only affect linux HiDPI getdown splashscreen).
If Jalview is installed in a folder that's not writable to the user, getdown refuses to continue if it cannot write a lock file before trying to update.
If there is no network, getdown is sensible enough to carry on launching without performing an update. This should be the behaviour if the Jalview install folder is not writable.
Note that the launcher.log will have to be written elsewhere (e.g. %APPDATALOCAL%\Jalview).
1) Enable getdown launch when getdown dir is not readable.
Other improvements:
2) Synchronize jalview.bin.* (in particular HiDPISetting)
3) Enable holding down SHIFT key at startup to revert to the "install/getdown.txt"
4) Attempt to set the HiDPISetting property immediately at startup (this might not work anyway and would only affect linux HiDPI getdown splashscreen).
