Why Is the Block Diagram Disabled?

[diarmaede]

What did I do now?  Please look at the attached image.  A VI that I am using as a subVI in various different programs suddenly started looking like I had used application builder to create an exe file out of it (But I didn't!!).  The only options are Start and Run Continuously, and the block diagram is disabled.  What did I do to get myself in this mess?  How do I undo whatever I did, so I can edit the block diagram again?  Any help or suggestions would be greatly appreciated.

Thanks!

[altenbach]

Did you save it without block diagram?

It would be much easier to tell if you could attach the actual vi.

[diarmaede]

VI attached.  Don't tell my legal dept.  Thanks for your help.

I didn't know you could save a VI without the block diagram.

[altenbach]

Did you ever built a source distribution with the option set to remove the diagrams? In this case, the original must still be around somewhere.

Since LabVIEW 8 you can no longer simply save without block diagram and you would not be able to upgrade such a VI to LabVIEW 2011, which it is now. (details)

Of course it is possible that there is some corruption, but looking at the memory usage, the block diagram is blanked out.

[johnsold · Accepted solution]

You somehow managed to save it without a block diagram.

Go back to the last working back up and start from there.  You do have backups, right?

Lynn

[diarmaede]

I have no idea what I did.  Everything was "normal" a few days ago, then suddenly, POOF!

Ain't software development fun?!

I found a version that has the block diagram intact, so I will just replace all the goofed up versions with the working version and proceed.

Thanks to both of you for your help.  Tis much appreciated!

[johnsold]

Make an extra back up copy until you are sure you won't do it again!

Lynn

[diarmaede]

"Make an extra back up copy until you are sure you won't do it again!"

Now c'mon.  That could never happen! 

(I promise I'll make multiple back up copies of the one that works!)

Thanks again.

[SnowMule]

Source Code Control... is a good thing. :nod

[diarmaede]

Oh, what I wouldn't give to work for a place where LabVIEW development was taken seriously enough that management gave me the time and resources necessary to impliment a source control system.  I suppose I really should do the research on my own and create a system that works for me.

Why is it that everywhere I work, people seem to think of LabVIEW as nothing more than data logging software, even after I show them time and time again that my code does much, much more than that?  "It's just LabVIEW," they say over and over again, "Why would it take you so long to develop the test code we need?"

I'm really fed up with that attitude.

Sorry to vent at all of you, but if there were ever sympathetic ears out there, they are on you folks.

Cheers,

FB