Alright... what appears to have happened is some sort of mystery linking between the palettes and the *.mnu files. It appears that the dir.mnu file of one of the subfolders in user.lib got "corrupted", byt which i mean it was a vaild *.mnu file, but no longer matched what the palette was displaying. How this might have happened it am not sure (might have been an issue with revision control and the fact that the palette editor tries to create some dir.mnu files automatically). At any rate, I deleted all of the mnu files in the offending folder and created them from scratch and this solved the problem.

There experience prompts me to complain that the palette editor is a shabby piece of work that (IMO) could use some serious attention in the next release of LabVIEW.

At 05:58 PM 6/7/2004, you wrote:
I am trying to add a submenu to the user.lib palette... every thing behaves as usual until I click "Save Changes". When I click that button, LabVIEW goes away, without saving the changes.

There is no error message when LabVIEW fails... it simply closes the palette editor and then never returns. I can watch it vanish from task manager. Also, when I restart LabVIEW there is no information about any internal error for me to investigate. In fact, there is basically no information available for me to start searching for the cause.

So, if anyone has seen this before and has any idea what is happening.. please help! :)

George Gatling Applied Technology Division, SFA Inc. Space Physics Simulation Chamber US Naval Research Laboratory 202-404-5405 (phone) 202-767-3553 (fax)

If trees could scream, would we be so cavalier about cutting them down?
We might, if they screamed all the time, for no good reason. --Jack Handy






Reply via email to