Fix QProcess failing to launch autoscoper.exe on Windows

[NicerNewerCar]

• Removed usage of QProcess.start(executablePath) in favor of:

  QProcess.setProgram(executablePath)
  QProcess.start()

• Fixed bug with AutoscoperM refusing to reconnect to Autoscoper server if the connection was severed outside of the Slicer environment (ie. Autoscoper crashed and you tried to relaunch it from Slicer)
• Updated .gitignore to include build directories
• Closes Issues #15 and #18

[amymmorton]

I don't think I can test until I build (after the slicer build from source is complete)- unless you want to commit and we test the extension directly?

[jcfr]

@amymmorton you could modify the file locally based on the content proposed in the pull-request and restart Slicer.

[amymmorton]

I attempted to make local changes (C:\Users\amorton1\AppData\Local\slicer.org\Slicer 5.3.0-2023-03-27\slicer.org\Extensions-31693\SlicerAutoscoperM\lib\Slicer-5.3\qt-scripted-modules\AutoscoperM.py) lines 347-353:

with changeCurrentDir(executableDirectory): logging.info("Starting Autoscoper %s" % executablePath) self.AutoscoperProcess.setProgram(executablePath) self.AutoscoperProcess.start() self.AutoscoperProcess.waitForStarted()

    slicer.app.processEvents()

After slicer restart- the app launches successfully:

[FD] Initializing OpenGL... [FD] Initializing OpenCL-OpenGL interoperability... [FD] Initializing OpenGL... [FD] Initializing OpenCL-OpenGL interoperability... [FD] New Client is Connected...

Trials open successfully

[amymmorton]

machine restart did not change the error