Broken Arrow with Case Structure Input Selector

[Sundar...]

Generally We get a broken arrow when a case structure 

is wired incorrectly to its case selector .

I found that even after this is fixed, the arrow remains broken.

however when you click on the broken arrow, the VI 

starts to execute instead of highlighting the error.

Seems like a compiler Issue.

I want to know if anyone has faced this issue.

I am currently using LV 8.6

Regards,

Sundar.

[muks]

Can you post a screen shot?

[chrisger]

Hi there

These things happen since long long time. Be prepared for one of those "insane object" messages to pop up in the future.

1. Make a backup of all your code

2. I suggest to delete the related code (case structure, wires etc.) until there's no strange behaviour anymore. Otherwise you VI may crash in the future with the danger of data loss (well there are possibilities to try to delete "insane objects" in case of such a message, but this may not work in your case) 

[Ben]

---

SUNDAR.N wrote:

Generally We get a broken arrow when a case structure 

is wired incorrectly to its case selector .

I found that even after this is fixed, the arrow remains broken.

however when you click on the broken arrow, the VI 

starts to execute instead of highlighting the error.

Seems like a compiler Issue.

I want to know if anyone has faced this issue.

I am currently using LV 8.6

Regards,

Sundar.

---

I can confirm that. I HAve seen it with type defs as well as LVOOP classes.

I have never been able to reproduce it on demand but it always seesm to be associated with situations where a type or class definition was changed. I think I have seen this issue on and off from LV 8.2 thru LV 8.6.

Ben

Message Edited by Ben on 07-31-2009 06:59 AM

[Sundar...]

Yes,

Insane Object still seems to be the worse Nightmare out in LabVIEW.

During this crash atleast an option to save current data has to be provided

in order to save the current VI`s, since most of effort is lost with this.

Sundar.