terrill

I am a Lead Test System Engineer 13 years experience in test system development in RF and communications fields. I have 13 years experience in LabVIEW starting with LabVIEW 3.1. I would like to stay local in South Florida but would relocate for the right position. I would also be available for project/freelance work.

Linkedin Website

Terrill

That doesn't provide the initialization guarantee that Jimi is hoping for -- a scoundrel programmer on your team could still drop the class directly instead of dropping the initializing VI.

I don't see the difference. a scoundrel programmer could drop the the class and not use this method. One way you insist the programmer drops a vi to construct a class, the other you insist the programmer drop a method everytime he construsts a class. I don't care either way but I do not see any improvement. Either way you have to do extra and define rules as a work around for this limitation. Programmers choice.

No method exists. This is noted in the design documents white paper as a limitation that needs to be addressed in future versions.

Write a constructor. It will contain the class object and set data for the class. Instead of putting the reference on the diagram you put this vi.

Has anyone use the import dll function to import the functions of either of these to Labview. I would like to use the functionality but I do not like giving control to a script from another language.

Terrill

I have an application that I am trying to automate the has a manual step using MTTY.exe to communicate over a serial port to a product. Does anyone know if this TTY communication can be replaced by all LabVIEW code or a call to other software? I would appreciate any help. Thanks.

Terrill