LV 7.0 extremly unstable while working with user events during edit time

[chrisger]

hi

i create and register several user events inside an initializing vi and then pass the registered events to the event structure using dynamic events in my top level vi. all works fine untill i do some changes to the registered events, e.g. changing names, datatypes or add/remove some events. when doing so my LV 7.0 chrases after opening the top level vi (exception error, no *.cpp errors). all changes i made are going to nowhere. i understand that after the changes i made the registered events in my init.vi-indicator dosn't match the events in my event structure, but i can't understand that LV chrashes.

here are my questions:
1. is it a known problem to LV 7.0?
2. should i reinstall LV 7.0
(i have LV 6.x and 7.0 on my machine)?
3. is there a fix?

thanks in advance

greetings
chris

[ColoradoRuss]

I am having similar problems with LV 7.1. I have two apps that make extensive use of property nodes, and I found a couple bugs with the error cluster out of property nodes nodes. One is scheduled to be fixed in the next release of LV. The other was a new report to tech support. If you dont wire the error clusters, that seems to helps. The second bug is with the probe on the clusters. The node did not work the same when it was probed and when it was not. I know it seems vague, but I am not sure what the exact cause of the problems are. Just try unwiring some of them and dont probe them (use an indicator). I have actually had my system crash 5 or 6 times in the past 2 weeks, and two of my .vis were completely hosed. I had to start over.

[Caroline Bright]

Hello Chris,


I have been looking into your problem and have come across one possible known bug in LV 6.1 that may be showing itself in 7.0. If modifications are made to the typedef of a registered event the vi will crash. I was hoping that you could post a small piece of your code and instructions on how to reproduce the crash. This way I can see if this is the same bug, a programming error, or an installation error. I can then determine if there is still a bug that needs to be looked into by our research team.

Thanks,
Caroline
National Instruments