Windows API Function Utilities (32-bit) for LabVIEW

Publish Date: Jun 19, 2009 | 9 Ratings | 2.89 out of 5 | Print | 9 Customer Reviews | Submit your review

These VIs make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, etc); managing applications (run application, quit application, print file, etc); adding and removing network resources; keyboard filtering; and system utilities (mouse cursor position, windows path, screen resolution, system path, etc). These VIs are intended for use only on 32-bit Windows platforms.

These utilities were originally created with LabVIEW 3.1, but have been recompiled into LabVIEW 6.0 and 8.6.1 for your use.
The archive contains the files saved with LabVIEW 6.0.
The archive contains the files saved with LabVIEW 8.6.1.

The abilities of the VI Server supersede the functionality of the VIs. National Instruments recommends that you use the VI Server functionality for new applications. Implement calls that the VI Server does not support through the Windows API directly by using a Call Library Function node in a more recent version of LabVIEW.


Related Links:
Product Manuals: Capabilities of the VI Server (LabVIEW 8.5 help)
Product Manuals: Call Library Function Node (LabVIEW 8.5 help)
Product Manuals: Example 3: Call the Win32 API (LabVIEW 8.5 help)
KnowledgeBase 1GRAN2U0: Where Can I Get Help Calling Windows API Functions from LabVIEW?
KnowledgeBase 203EA3XC: LabVIEW.LIB Error When Calling a LabVIEW DLL Built with VIs That Use External Code


Back to Top

Customer Reviews
9 Reviews | Submit your review

Request Update to LabView 2013 - Nov 26, 2014

Windows APIs are useful for non-LabVIEW windows. Please update to LabView 2013. thanks in advance

VI Server doesn't work for non-LabVIEW windows - May 19, 2014

VI Server doesn't work for non-LabVIEW windows. Therefore, it does NOT supersede LabVIEW WIN API VIs. George Zou

 - Feb 26, 2014

In what ways does VI server do the same things as Windows API calls? Do you mean through property and invoke nodes? Is this what NI means by VI Server?

View more reviews

Bookmark & Share






Rate this document

Answered Your Question?
Yes No