Hi,
LabVIEW does take advantage of multiprocessor computers by automatically multithreading LabVIEW applications. LabVIEW, however, handles threading automatically as this is hidden from the end user. In order for LabVIEW to specify a piece of code to be a safe thread, that thread must not access global resources, as this will cause the thread to be unsafe. The thread safe code cannot call non thread safe code and therfore does not allocate another thread for the Mathscript node. The mathscript node uses ActiveX technology to programmatically open up MATLAB(R) software and since the LabVIEW does not know the safeness of MATLAB(R), LabVIEW specifies that this part of the code should run in the safest mode possible and therefore does not allocate another thread for this execution.
I hope this helps,
Regards,
Nadim
Applications Engineering
National Instruments
