Patch windows installers for VATES

[Owen Arnold]

MantidPlot cannot be used to view a workspace because Mantid has no knowledge of the VATES libraries installed afterwards in a separate location and they are therefore not dynamically loaded.

Fix is to introduce additional environmental variable that MantidPlot can pick up at runtime. We might look at doing something more elegant in the future.

[Owen Arnold]

In [14767]:

refs #3747. Verified that env variable can be added/removed.

[Owen Arnold]

In [14768]:

refs #3747. Extract Env variable.

[Owen Arnold]

In [14776]:

refs #3747. Give a better error message in MantidPlot if visualisation is not available under windows.

[Owen Arnold]

I've checked that this is picking up the correct libraries using ProcessExplorer now. Also gives a sensible error message if Vates package has not been installed.

[Owen Arnold]

For testing:

Test 1

• Install Mantid
• Install MantidVates
• Open MantidPlot
• Open the LoadMD algorithm
• Provide the file ...\Test\AutoTestData\MAPS_MDEW.nxs as the file argument
• Run the algorithm
• Right-click the workspace and select the Visualisation option. This should open The Visualisation window showing the workspace you have just selected.

Test 2

• Close everything
• Uninstall MantidVates
• Open MantidPlot
• Open the LoadMD algorithm
• Provide the file ...\Test\AutoTestData\MAPS_MDEW.nxs as the file argument
• Run the algorithm
• Right-click the workspace and select the Visualisation option. An error message should be printed to the MantidPlot console.

[Peter Parker]

The workspace is displayed in Yates for test 1.

"InterfaceManagerImpl::createVatesSimpleGui is null" is displayed in the console for test 2.

Both tests pass.

[Stuart Campbell]

This ticket has been transferred to github issue ​4594