Martin Craig authored 4 years ago and Paul McCarthy committed 4 years ago

Also minor bugfix - allow forward or backslash after \\wsl$ when
specifying FSLDIR as a WSL network share

Martin Craig authored 4 years ago and Paul McCarthy committed 4 years ago

The problem here is not that it can't find the folder but that FSLDIR
suggests a WSL installation but does not match the format required to
identify the distro folder.

Martin Craig authored 4 years ago and Paul McCarthy committed 4 years ago

This requires  WSL 2.0 but enables FSLDIR to be a genuine
WIndows path so that atlases and standard data can be loaded
transparently. It also means we no longer need FSLWSL environment
variable, just to be a bit careful with path mapping

Martin Craig authored 5 years ago and Paul McCarthy committed 4 years ago

This means that users who have FSL installed in Windows Subsystem
for Linux can call the wrappers directly from a Windows python
program (after setting the environment variable FSLWSL=1)

module-level functions. No changes to functionality

gives $FSLDEVDIR precedence, and also allows a global override.

was always returning unknown. Also adjusted wx properties so they can be
queried if a gui is not open, but is available.

presence of 'mesa' or 'gallium' does not imply software rendering. And
llvmpipe is fast, so should be treated as hardware.

VNC-like environments.

previous commit.

using a software or hardware GL renderer.

initialisation. Async.idle still honours after argument, even if a
wx application is not running.

Platform.canHaveGui, can be used to tell whether we are able to create a
GUI. Async modified to use platform.haveGui instead of performing its
own test.

platform module.

we're running locally or over ssh.

log.memory .. all the __init__ stuff will make its way over to FSLeyes.

bug (http://trac.wxwidgets.org/ticket/16440) in FSLDIRDialog.