seemingly unnecessary error messages in labview 8.5

[DustinS]

A "diagram disable structure" did not have an "enabled" section, producing an error that did not allow the vi to run.

This took me a while to find, however, since it was at the bottom of a list of  "front panel control has undefined type" errors (which disappeared, once I enabled one of the subdiagrams). This even happens when the "diagram disable structure" has nothing in it.

I've also noticed extra "undefined type" errors popping up in other cases.

Can someone provide a model of the internal workings of labview in which these errors make sense?

[Norbert_B]

Dustin,

what version of LV are you working with?
In LV 8.5, the errorlist says:
Block Diagram Errors:
- Diagram Disable Structure: Diagram/Conditional Disable Structure has no active diagram.

Norbert

[Mathan]

---

Norbert B wrote:
Dustin,

what version of LV are you working with?

---

In the message subject itself, dustin told LV8.5

[Norbert_B]

---

@Mathan wrote:

In the message subject itself, dustin told LV8.5

---

Well, thats correct.....
Ok, in this case, please post the VI which generates that error.

Norbert

[dsoodak]

Here is a shortened version of the project which contains only what is necessary to produce the error messages I described.

[Norbert_B]

Dustin,

the diagram disable error is "normal", so there is nothing wrong about that.
It is strange that the other error occurs.
I haven't managed to reproduce it with other typedefinitions. Can you verify if it is connected to a special type of typedefs?

Norbert

[Mathan]

In first post his name was dustinS and 5th post it was dsoodak. Same user in different names?

[dsoodak]

I originally signed in as DustinS, but when I clicked on the link from the "you have a reply to your message" e-mail, in signed me in as dsoodak.

I think I ended up creating a different user name in IE.

[dsoodak]

>>I haven't managed to reproduce it with other typedefinitions. Can you verify if it is connected to a >>special type of typedefs?

I tried it with several versions of this one, though it stopped happening when there were no invisible items in the Chart.ctl cluster. Then it didn't happen again (when I made the item invisible again).

I'm still getting it in my full project. It doesn't seem to be causing any other problems, though. It just takes a bit longer to locate the relevant error message.