I’ve attached a zip of the directory structure for those on mac/linux that would like to try.
The procedure below is only for those that wish to try and run the application under Mono. If you are on Windows, you don’t need to do that as you can run it natively If you are on Mac or Linux, then you will need to run under Mono.
On Windows, you can download the Mono installer HERE. I have not had good luck with the x64 install as it doesn’t install GTK by default and the environment isn’t correct when I install that separately. But, on Win10 x64 you can install the x32 version of Mono and it seems to runs fine thought it does appear to exhibit more sensitivity than the native dotnet in terms of acquisitions hanging while changing control settings. But left alone it ran 50k acquisitions before I stopped it.
Once mono is installed on your platform, open a mono command prompt and navigate to your QA40x unzip location as shown below. The type mono qa40x.exe to launch the app
On Windows under Mono the current release has giant status bar region, but that has been fixed already for the next release. Plug-ins should work–attached is a plot from a frequency response chirp.
Remote access via REST appears to work.
For folks not familiar with what Mono is doing, they have re-created the WinForms experience in GTK–no small feat. DotNet used to be very, very tightly tied to the Windows UI. That has been evolving over the last decade as Microsoft ventures out new directions. But what Mono has done is very impressive. Since they use GTK as the gui, and gtk exists cross platform, that means there should be a lot of commonality between the platforms. That is, quirks seen on Windows should also be seen on other platforms when running on Mono.
In any case, those on Linux/Mac, please try and and share what you see. For the next release the directory structure will be posted as a separate zip on github.
QA40x.zip (3.2 MB)