PopUpMenu's "work", but crash on exit when compiled.

Question

I've been fooling around with PopUp menu's using the USER32 DLL. One question I still have is should I destroy all submenus, or will destroying the top popup destroy all the submenus. It doesn't seem to make a difference.
Also, when I compiled a demo program, I noticed the USER32.DLL showed up in my data folder. The program seems to work, until I close the window, when I get a bomb window titled "Quincy Fatal Error". The text in the window is
Could not attach to the application
Windows Error Code = The parameter is incorrect.
The program seems to work fine, I can start and restart it all I want. It's when I click on the CloseWindow X in the upper RHCorner that I get this error. I've looked at some other
code on the forums and it looks like everything is OK.
Has anyone else seen this behavior, or could steer me in the right direction?
Thanks, Bob
Attachments:
PopUpTesty.llb ‏125 KB

Answer 1

Wiebe,
I'm glad I was able to help you, even if I didn't realize I was doing it.
I don't know if this info means anything, but I ran a test to see what would happen.
I wrote a VI that creates a PopUpMenu with one entry, a submenu. The submenu had 10 items in it. I then just deleted the parent menu, and didn't do anything with the child menu. (I never called TrackMenu, I just created and destroyed. I assume this is not a factor)
Then I brought up the Win2K Task Manager, and included handles in the Process Window. I noted the numbers for Handles and available memory. I started my program. The handles number never seemed to change. Availiable memory would start shrinking, and then jump back up to where it started. (This is
what I expected to see.) After 5,000,000 iterations, everything still seemed the same. While the actual memory requirements for menus is probably small, I would think I would have seen the effect of 5 million orphan menus. Note that if I comment out DestroyMenu altogether, AppendMenu fails after about 1200 iterations (and LabVIEW bombs on the first user interaction)
The reason I'm so interested in this is because I only have 2 VI's to support PopUpMenu's; One to create them and one to track them. After I get the MenuItemID, I destroy the hMenu I tracked in the "Track" VI, making everything nice and neat (to me anyway).
All this is related to the TreeView ActiveX control that you helped me with earlier. In this case, if a user MouseDown's with the right button, I generate a PopUpMenu based on data the node (if any) represents. The Tag property of the Node tells me what "kind" of node it is (a value for a Case selector), which then grabs the appropriate data to build the PopUpMen
u (along with any submenus).
Once again, thank you very much for your help. I've learned a great deal in the last week or two trying to get my LV programs do what I want them to do.
Bob