Wow, that's a huge amount of input. :-) Thanks to all.
So how to build up a single CLFN is partly clear.
With wizard import of the function from .dll with .h-files, I still strugling. The wizard in LV partly recognized some functions from the .h-file, but not all (see picture). It depends which .h-file I choose. At the end, no fuction was usable.
I allready tried to include in an .h-file the command #include "fileX",... . But with no sucess --> LV crashed.
In the docu is explicit written that you can develop your own driver. So it should work.
I suppose, it probably will be written indirectly in the docu - maybe via the examples. Logical thinking. --> try & error.
When it makes sense to work with callback function? Only, when I need this optional part of function?
As I understand you all correct.
The .lib-file is importand for the .dll. Is there a way to work with the .lib file in LV - 3third party software? (attached)
The .lib-file can be loaded on two ways: (1) By calling LoadLibrary()/GetProcAddrss() or (2) by linking the import library. But both ways are senseless for LV.
The full/complete .h-file is nice for me as LV developer. But not necessary, when I have the docu with the description of function for the .dll. With the .h-file and the wizard, I can simple generate all functions automatically at once. With the docu I have to programm every function node according the description on my own.
cifX32DLL.lib