Hello All -
@miniMe - I couldn't help but notice from the information that the window you are looking to interact with is part of the standard TestStand installation (modelsupport2), for which the source code is readily available. While modifying modelsupport2 is not for the faint of heart, your task is specific enough that I was able accomplish it with only a handful of lines of code (be sure to copy the modelsupport2 files to the public location before making changes). The important components are below:
The application that is going to be sending the UUT number can send the WM_COPYDATA message to the TestStand application. Using this message is pretty straightforward, and allows you to pass data (such as a UUT string) across process boundaries. Here is the relevant piece from my small test app that sent the message:
#include <windows.h>
#define UPDATE_TEXT_MSG (WM_APP + 1)
...
COPYDATASTRUCT dataToPass;
char msg[80];
strncpy (msg, "test message", sizeof (msg));
dataToPass.dwData = UPDATE_TEXT_MSG;
dataToPass.cbData = sizeof (msg);
dataToPass.lpData = msg;
// gHostHwnd was obtained from EnumWindows
SendMessage (gHostHwnd, WM_COPYDATA, 0, (LPARAM)&dataToPass);
The receiving end of this is also pretty straight forward. In the modelsupport2 project in CVI, you just need to make a couple modifications to the uutdlg.c module. Specifically, you need to use InstallWinMsgCallback in the function DisplayUUTInformationDialog to receive the WM_COPYDATA message. It should look pretty similar to this:
// existing code in uutdlg.c
errChk( panel = LoadPanelEx (0, UIR_FILE_NAME, UUTPANEL, __CVIUserHInst));
RecessFrame (panel, UUTPANEL_SERIALNUMBER);
AlignRingButtonWithString (panel, UUTPANEL_PREVUUTLIST, UUTPANEL_SERIALNUMBER);
// Nick Beer - added for customer functionality...
errChk (InstallWinMsgCallback (panel, WM_COPYDATA, SetUUTNumberCB,
VAL_MODE_INTERCEPT, &panel, &postingHwnd));
Finally, again in uutdlg.c, you need to define the implementation for the WinMsgCallback. My implementation looked like this:
#define UPDATE_TEXT_MSG (WM_APP + 1)
...
int CVICALLBACK SetUUTNumberCB (int panelHandle, int message,
unsigned int* wParam, unsigned int* lParam, void* callbackData)
{
PCOPYDATASTRUCT pUUTInfo;
int panel;
if (message == WM_COPYDATA)
{
pUUTInfo = (PCOPYDATASTRUCT)(*lParam);
panel = *(int *)callbackData;
if (pUUTInfo->dwData == UPDATE_TEXT_MSG)
SetCtrlVal (panel, UUTPANEL_SERIALNUMBER, (char *)pUUTInfo->lpData);
}
return 0;
}
Also - don't forget to call RemoveWinMsgCallback. Once you've made these changes, you just need to rebuild modelsupport2.dll, and the messaging should work as expected.
Feel free to let me know if you have any questions about this. I left out some of the TestStand specifics assuming you may know about the public directories etc. Let me know if you're unsure about any of this.
@dummy_decoy - I don't have a complete answer to your question, but want to point out that one thing that must be remembered about CVI is that it was and is intended to be multi-platform. This is the primary reason our controls and panels don't always play nice with the Win32 api. We've done what we can to make sure there are workarounds for users who need this functionality - as I hope my solution demonstrates - and are always open to suggestions on how we can improve interoperability with the Win32 platform.
I personally don't have any experience with the other specific aspects of your question, and so am not comfortable making any statements about them at the moment.
NickB
National Instruments
