LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to add GetValueByPointer XNode in LabVIEW Application

Not a drop in replacement by far, but another alternative if there are requirements to parse the returned pointer in more detail could be: https://www.vipm.io/package/easlib_memory_manager/

 

But beware, it's not for the faint hearted who just wants to replace the GetValueByPointer XNode. You do need to understand how the memory pointer is layed out in memory and what elements in what order you want to retrieve. Stll it can be an alternative to have to write a separate shared library in C to adapt between C pointers and structures and LabVIEW data types including clusters.

 

One library using the Memory Manager library would be: https://www.vipm.io/package/easlib_win_credentials/

It's not rocket science, just a small library letting one interface to the Windows credential store (certificates). I had written in the past a library that was using an intermediate shared library to do the structure to LabVIEW cluster conversion but supporting both 32-bit and 64-bit made it necessary to compile two separate shared libraries with each change. By using the Memory Manager library instead, I could completely avoid the intermediate shared library. It's not trivial work, in fact if you don't really know in detail how a C compiler arranges elements in a structure, it would be easier to write an intermediate library in C and let the C compiler deal with those details. But if you do know, you can make a lot of things that used to require an intermediate library in the past, or very involved Flatten/Unflatten with byte parsing, and endian and alignment and platform specific conditional code.

 

Rolf Kalbermatter
My Blog
0 Kudos
Message 11 of 11
(57 Views)