NI TestStand
Teststand 2017 32-Bit - UUT Information Dialog in Windows 10 not displaying properly
Solved!
Dharani, Thanks for the assistance on this. I have my dialog modified and improved. I needed to make several changes in paralleluutdlg.c in order to reposition the stop, terminate, abort, and exit buttons. (The entire window now resizes when I change the number of sockets.) After that a bit of cleanup and some coloring at the request of the factory.
Thanks again for pointing me in the correct direction. BTW, I did this in CVI 2017 (because we are still using TS 2017). I will look into updating to 2020, but it is not a priority at this time.
(And you were correct with your initial impression that this was indeed a modified dialog!)
Thanks again!!!
I thought I would document the changes that I had to make to my dialog in the chance it would help someone else. (these are all in paralleluutdlg.c)
1) Change the number of sockets to the number desired. This causes the container to resize (no scroll bar if number selected is equal to, or less than this number)
2) Now my socket windows are the correct sizes, however, they cover the stop, abort, terminate, and exit buttons. - need to adjust those along with the main panel size.
At line #233 in my project in MakeNewTestSocketCtrls() function:
//resize main panel and position buttons
int panelWidth = 0;
int socketPanelHeight = 0;
int socketPanelTop = 0;
int doneButtonHeight = 0;
int blankSpace = 5;
//get starting position to reset the done button top and resize main panel
//get height of panel holding sockets
GetPanelAttribute (childPanel, ATTR_HEIGHT, &socketPanelHeight);
//get top of panel holding sockets
GetPanelAttribute (childPanel, ATTR_TOP, &socketPanelTop);
//get height of done button
GetCtrlAttribute (panelId, PUUTPANEL_DONE_BTN, ATTR_HEIGHT, &doneButtonHeight);
//pad blankSpace to make it look a bit better
int new_done_control_top = socketPanelTop + socketPanelHeight + (blankSpace *2);
//get the main panel width because we need it when we resize
GetPanelAttribute (panelId, ATTR_WIDTH, &panelWidth);
int newMainPanelHeight = new_done_control_top + doneButtonHeight + blankSpace;
//set new size of main panel
SetPanelSize(panelId, newMainPanelHeight, panelWidth);
//set buttons so they are positioned correctly below socket panel and above bottom of main gui
SetCtrlAttribute (panelId, PUUTPANEL_DONE_BTN, ATTR_TOP, new_done_control_top);
SetCtrlAttribute (panelId, PUUTPANEL_ABORT_ALL_BTN, ATTR_TOP, new_done_control_top);
SetCtrlAttribute (panelId, PUUTPANEL_TERM_ALL_BTN, ATTR_TOP, new_done_control_top);
SetCtrlAttribute (panelId, PUUTPANEL_STOP_ALL_BTN, ATTR_TOP, new_done_control_top);
3) Ok, now the panel looks ok, factory wants the sockets to start with "1" instead of "0" (Note that this is display ONLY, does not affect actual sockets)
simply add 1 to testSocketIndex - again, this is display only and will not affect the actual sockets.
This is done on line # 452 in my project (note that my line numbers may be slightly different than yours because I have been working on this file and added/deleted lines. This is near the end of the function MakeNewTestSocketCtrls()
}
// initialize ctrls
//set tmpNumBuf to testSocketIndex +1 so that 1 through 8 are displayed. This is less confusing to test operators.
sprintf(tmpNumBuf, "%d", testSocketIndex +1);
errChk( SetCtrlVal (childPanel, newTestSocket->ctrls[kTSCtrl_TestSocketIndex], tmpNumBuf));
errChk( RecessFrame(childPanel, newTestSocket->ctrls[kTSCtrl_SerialNum]));
4) Add the color coding to the sockets so they match the wiring harness cable colors the operators plug into the units.
These are near the top of RefreshTestSocketCtrls function near line #782
int VAL_BROWN = 0xA52A2AL;
int VAL_ORANGE = 0xFF5522L;
//set the socket colors for easy operator identification
if(testSocketIndex == 0)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_BLACK));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_WHITE));
}
if(testSocketIndex == 1)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_WHITE));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_BLACK));
}
if(testSocketIndex == 2)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_BLUE));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_WHITE));
}
if(testSocketIndex == 3)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_YELLOW));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_BLACK));
}
if(testSocketIndex == 4)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_BROWN));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_WHITE));
}
if(testSocketIndex == 5)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_ORANGE));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_BLACK));
}
if(testSocketIndex == 6)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_CYAN));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_BLACK));
}
if(testSocketIndex == 7)
{
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, VAL_DK_MAGENTA));
errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_COLOR, VAL_WHITE));
}Also have to comment out this line because it resets these sockets to default colors.
near line #1006
//TODO: I commented this out because it resets the socket colors to default. I put this note in case it causes issues.
//errChk( SetCtrlAttribute (childPanel,testSocketData->ctrls[kTSCtrl_TestSocketIndex],ATTR_TEXT_BGCOLOR, bgColor));
5) Next up, factory wants the failures displayed in the status box and want the Main Sequence name displayed somewhere on the UUT Information Dialog. I will have to see if/how to do this and may revisit this when I find a way.
Thanks,
