It wants a char; then says it's too small

Question

Hello,
I have created a UI for a TestStand program in LabWindows/CVI; and it's causing me headaches. The problem is two out of several dozen of (nearly) identical function calls:
GetCtrlVal(panel, UUT_Test4, &gTestTemp); basicTest[3] = gTestTemp;
GetCtrlVal(panel, UUT_Test5, &gTestTemp); basicTest[4] = gTestTemp; //Error here
GetCtrlVal(panel, UUT_Test6, &gTestTemp); basicTest[5] = gTestTemp; //Error here
GetCtrlVal(panel, UUT_Test7, &gTestTemp); basicTest[6] = gTestTemp;
gTestTemp is defined as a static int. The functions are called in a callback function, which runs when the user clicks the "Ok" button in my UI.
When I run my TestStand program and I press said OK button, I get a fatal runtime error: "Invalid argument type: found 'pointer to int', expected 'pointer to char'".
I attempted to fix this issue by defining a new value, gTestTempC, as a static char and using it to retrieve the result for only these two function calls:
GetCtrlVal(panel, UUT_Test4, &gTestTemp); basicTest[3] = gTestTemp;
GetCtrlVal(panel, UUT_Test5, &gTestTempC); basicTest[4] = gTestTempC; //Error here
GetCtrlVal(panel, UUT_Test6, &gTestTempC); basicTest[5] = gTestTempC; //Error here
GetCtrlVal(panel, UUT_Test7, &gTestTemp); basicTest[6] = gTestTemp;
This results in the fatal runtime error: "Argument too small".
I have gone into my *.uir file and have verified that there is absolutely no difference between the checkbox control elements of the functioning and the error-bringing function calls (apart from their name and their label).
Does anyone have any idea what may be the problem here?
~Cheers,
D.W.

Answer 1

The code that was giving me trouble is:
static int gTestTemp;
static int basicTest[7];
//Some code here
int CVICALLBACK DispTestUIDone (int panel, int control, int event,
void *callbackData, int eventData1, int eventData2) {
switch (event) {
case EVENT_COMMIT:
GetCtrlVal(panel, UUT_Test1, &gTestTemp); basicTest[0] = gTestTemp;
GetCtrlVal(panel, UUT_Test2, &gTestTemp); basicTest[1] = gTestTemp;
GetCtrlVal(panel, UUT_Test3, &gTestTemp); basicTest[2] = gTestTemp;
GetCtrlVal(panel, UUT_Test4, &gTestTemp); basicTest[3] = gTestTemp;
GetCtrlVal(panel, UUT_Test5, &gTestTemp); basicTest[4] = gTestTemp;
GetCtrlVal(panel, UUT_Test6, &gTestTemp); basicTest[5] = gTestTemp;
GetCtrlVal(panel, UUT_Test7, &gTestTemp); basicTest[6] = gTestTemp;
QuitUserInterface(0);
break;
return 0;
Upon calling the function TestUIDone with event EVENT_COMMIT, I got an error on the lines containing UUT_Test5, UUT_Test6 and UUT_Test7: "found 'pointer to int', expected 'pointer to char'".
As was suggested above, I declared an array of character values (char) that was, apparently, required to be at least 63 bytes in size (according to a new error):
static int gTestTemp;
static char gTestTempC[63];
static int basicTest[7];
//Some code here
int CVICALLBACK DispTestUIDone (int panel, int control, int event,
void *callbackData, int eventData1, int eventData2) {
switch (event) {
case EVENT_COMMIT:
GetCtrlVal(panel, UUT_Test1, &gTestTemp); basicTest[0] = gTestTemp;
GetCtrlVal(panel, UUT_Test2, &gTestTemp); basicTest[1] = gTestTemp;
GetCtrlVal(panel, UUT_Test3, &gTestTemp); basicTest[2] = gTestTemp;
GetCtrlVal(panel, UUT_Test4, &gTestTemp); basicTest[3] = gTestTemp;
GetCtrlVal(panel, UUT_Test5, gTestTempC); basicTest[4] = gTestTempC[0];
GetCtrlVal(panel, UUT_Test6, gTestTempC); basicTest[5] = gTestTempC[0];
GetCtrlVal(panel, UUT_Test7, gTestTempC); basicTest[6] = gTestTempC[0];
QuitUserInterface(0);
break;
return 0;
This no longer throws any errors, but the basicTest array in no way resembles anything I enter into the UI. Additionally, I find it very odd that 63 bytes are required to store three true/false values (the UI control elements are checkboxes).
I can't really give you any more information about how to reproduce the error, since I'm not even sure myself how it came to be. Like I said, the UI worked fine and then stopped working although I changed nothing on that part of the program.
I will try to reproduce the error in a seperate program and let you know how that goes.
After finishing this one UI, I added another four to the same program. Perhaps those conflict in some way? I doubt they do since the other UIs all work fine, but I can't tell for sure.