Card specific DAQmx/LabVIEW Property Nodes

[Kira_T]

DAQmx allows you to change between active and open collector modes per line on cards that only support per port changes.  It is suggested that LabVIEW or DAQmx give a warning when trying to do this to tell you that the device only supports per port changes.  

Thanks!

Kira T

[JackDunaway]

+1. Generalizing this idea, it would be helpful to receive design-time compiler errors rather than run-time errors when working with the DAQmx API. Specifically, better type propogation user feedback by broken wires for incompatible types or methods that can be statically determined at design-time (as Kira T suggests), and also fewer overloaded functions. As an example, the VI Server API demonstrates these traits amazingly well, and as such is discoverable and intuitive. Perhaps, the next generational change of DAQmx could use LVOOP? 

[Darren]

Any idea that has received less than 5 kudos within 5 years after posting will be automatically declined.