Search the Community
Showing results for tags 'mac os'.
Found 2 results
-
Hello, I'm experimenting with porting my existing LabVIEW application from Windows to Mac OS X. The code uses several instances of 'Build Path' function in 'File I/O' functions sub-palette. The 'Name or Relative Path' input is being connected with a 'string' data type rather than a 'file path' data type. With some quick code change and checks, I've realized that it's better to use the latter data type, so that the separator character '\' in Windows is automatically interpreted as ':' in Mac OS. Some parts of the code, however, build up the string. E.g. a 'Format Into String' is used to -
I wrote a very simple vi for a friend of mine. Simple as in: this vi has no sub-vi's and all functions are from the standard palette. I was going to build an executable for him to run it, but it turns out he has a Mac and I am running on Windows. Even though I own 3 licenses of LabVIEW it appears that I have to purchase a whole new multi-thousand dollar LabVIEW license for Mac to be able to build it. Given the nature of the project, you can see why this is not a good solution for the situation. I am asking for a favor, that if anyone has the Mac OS version of LabVIEW if they wouldn'