LabVIEW
Use a wrapper to build a C++ Dll that calls a C++ .lib and Use the Dll is LabView
@BryanL wrote:Hi Emilie,Also, is there a way to find the window names of all open windows including not only labview vi windows but also windows from other applications? Some of my non labview applications will have their names changed dynamically during execution. I need to know their exact name to access them in a vi.
msdn.microsoft.com: Search for EnumWindows(). This will give you all top level windows.
Rolf Kalbermatter
Don't try to write a VI to call that function. That function requires a callback function pointer, something that is more or less impossible (well you can get it done but it is not worth the trouble) to create in LabVIEW. You will need an external DLL that does the enumeration and returns an array of strings to LabVIEW.
@BryanL wrote:Hi Rolf, thanks for the info. I will try to build a vi to call that function. For a more immediate need, I can use a downloaded vi that calls SetActiveWindow function, then use its output windowshandle to find the window name with a lvwuser32.dll function. The problem is this find window name function vi requires a windows reference input, which does not take the window handle output from the SetActiveWindow vi. How do i convert the window handle into a reference number? Thanks again.
The lvwuser32.dll also just uses window handles. Look inside those VIs and you should see that those window references are typecasted into uint32 and then passed to the Call Library Node if I remember correctly. You definitely should be able to typecast the (probably uint32) you get from your other function into the window reference that that VI takes. The window reference of the lvutil library is just a nice trick to make it refnum like so that you can not inadvertly wire something else to it (and confuse/crash Windows).
Rolf Kalbermatter
Someone wanted to be smart and used his own window handle type at some point. I would just copy the one from Get Widnwo Handle to the clipboard and replace the ones in the other VI with them. Technically they are the same as they are both a datalog refnum. But syntactically they are different since the typedef of the datalog is different and LabVIEW refuses to connect two different datalog refnums with each other. This is actually the reason to use such refnums for things like OS handles. A LabVIEW user then can't conect unrelated items together.
@BryanL wrote:Hi Rolf, you are exactly right that the two VIs I was trying to connect used different typecasts. So I modified one and made them the same, however, they still cannot connect. I have attached both. Please give them a try. (Both VIs were downloaded from this board with credit goes to the orignal authors)
Rolf Kalbermatter
