Closed jerlich closed 10 years ago
Verified with OSX binary release (Happens whenever record is pushed even with a headstage.) It runs ok within XCode, but then crashses when running the compiled code.
Verified with File Reader (irrespective of HW.)
The error was due to the unconventional (compared to Linux and Windows) file structure for OS X application bundles. Since the actual executable file is located inside a "package," the function "getCurrentWorkingDirectory" returned a null result in the pre-compiled binary, but not in the Xcode build. This is apparent when you check the data directory in the Control Panel, which was showing up as "/". Browsing to an actual folder fixed the problem.
I just updated the method for choosing the executable directory. A sensible data directory now shows up by default, and recording functions as expected. Try downloading the latest executable and make sure it works for you.
I'm trying to understand why it didn't throw an error when running in XCode or from the command line. Any thoughts?
I'm not sure about the technical details, but it's basically that "pwd" is undefined if you launch the app from the desktop. In that case, we have to find the absolute path to the executable, then go up three levels to the directory that's visible to the user.
Fixed as of Sept 22,2013
Steps: