08-26-2010 05:26 PM
Tools -> Advanced -> Mass Compile...
renders it readable.
08-26-2010 07:44 PM
You're welcome! I'm glad it is working for you. I know there is nothing worse than the feeling you've lost a lot of work. And sometimes redoing work a second time feels more painful than originally doing it.
Even if you don't use a formal source control system, it is a good idea to make backup copies of your project regulary. Do it when LabVIEW is closed (sometimes moving or copying things while a project is open increases the risk you cross-link files among your different copies.) Move it to a directory where it is unlikely for your project to search to find subVI's when it is looking for them. Zipping up your whole folder as a .zip file is a good suggestion as LabVIEW isn't going to look in there. And moving it to another drive such as a network drive so something like a hard drive crash won't wipe you out.
It's possible the mixed signal graph was the problem as well. I noticed it had data stored in it. I didn't see how much. But it might have increased the amount of memory used by the VI that you might have run out of memory when you opened it causing LV to crash. Hard to say. Fortunately the VI was saveable.
08-26-2010 07:48 PM
If the vi encounters an error or memory issue when running verse opening, then opening without running would avoid the error or memory error.
08-27-2010 03:16 PM
@Drewski wrote:
If the vi encounters an error or memory issue when running verse opening, then opening without running would avoid the error or memory error.
What are you trying to say and how does it related to this thread?
08-27-2010 03:24 PM
@Ray.R wrote:
@Drewski wrote:
If the vi encounters an error or memory issue when running verse opening, then opening without running would avoid the error or memory error.
What are you trying to say and how does it related to this thread?
Go back to the first page, and you will find your answer. In fact, he was replying to a question you asked him directly.
08-30-2010 07:29 AM
Thanks Tim..
Sorry Drewski..
I was having a bad NI forum week, last week 😞
@Drewski wrote:
If the vi encounters an error or memory issue when running verse opening, then opening without running would avoid the error or memory error.
I agree. I may have misunderstood something, however, my understanding was that the vi could not be opened at all. In other words, it wasn't running and causing an error.
Thinking about this, I wonder if it is possible to open a VI that is configured to run on open and as it starts to run, there's an error (maybe with the UI). Would it cause a situation where the front panel would not be seen? I would expect that the front panel would always show up followed by some error message. Have you seen a different behavior where the fron tpanel does not even show up?