LabWindows/CVI
how to force struct popups to work all of the time in CVI 8
Well,
...The IDE is mad at me again 
Actually, it had absolutely nothing to do with my re-arranging the structs in the header files earlier this week. There is definitely a bug in the IDE. I don't know what it takes to cause the popups to not appear yet, but I do know what does and what does not work to get them started again.
Of no use: recompiling the source file with the malfunctioning popup (Ctrl-K), making the entire build (Ctrl-M), marking the entire project for compilation and then making the build, switching between debug and release builds and then making the build, restarting CVI and then compiling, restarting CVI and making the entire build, deleting the build directory in the project folder and then recompiling the source file with the malfuncitoning popup
Only known resolution: deleting the build directory in the project folder and then making the build (will automatically detect the build directory is missing and will mark the entire project for compilation)
Again, this does not happen to all structs in the source file with the malfunctioning struct popups. But following the resolution outlined above, the popups immediately start working again. 
Orlan
#include <ansi_c.h>
#include <cvirte.h>
struct str_foo {
int i_test;
} gstr_foo[100];
struct str_foo2 {
int i_test2;
} *gstr_foo2;
int main (int argc, char *argv[]) {
if (InitCVIRTE (0, argv, 0) == 0) return -1; /* out of memory */
gstr_foo2 = calloc(100, sizeof(struct str_foo));
// gstr_foo[0]. //popup shows: i_test
// gstr_foo2-> //popup shows: i_test2
// gstr_foo[gstr_foo2-> //popup shows: gstr_foo, gstr_foo2
free(gstr_foo2);
return 0;
}
-----------------------
Compile this file first. Then uncomment the three gstr_foo lines, but do not recompile. Now position your cursor after the "." operator in the first previously commented gstr_foo. Press Ctrl+Space and it will complete 'i_test'. You can delete and re-enter the "." and the popup will alternatively appear with 'i_test'. Whatever, same thing. Now do it for gstr_foo2. It shows 'i_test2' as expected. But when you try the second gstr_foo, which has pointer notation inside of the array notation, the popup misbehaves. It should be showing i_test2 since this is the only available struct element in gstr_foo2. Notice the popup is at the beginning of the line, instead of at the end of "->" (where it should be) and that if you select something in the popup it either does nothing or it rewrites the beginning of the line.
Personally, I think this bug is what starts the whole mess for me. When I loose my popups, it tends to allow the outer struct to continue to show popups and the inner struct will not show popups anymore. I could not get this simple project to lose popups altogether, but it does show some misbehavior. It is a bit more complicated in my real code, something like: gstr_foo->widget.status = gstr_foo2[gstr_foo->thingy.doohickey].status; I loose popups for gstr_foo but popups for gstr_foo2 still work. And now the doggone 'delete the build directory' approach isn't even working anymore. 
Orlan
