Cannot change vi back to edit mode.

[JÞB]

---

@aputman wrote:

If the VI is still running....Ctrl-M will be greyed out.

---

Or reserved There I go missing an obvious piece of data and assuming the vi.state property is Idle

[momof4]

- the vi is attached (hope I did it correctly)

- the vi is not running when I open it

- checked the .ini file nothing in there that I can tell

THANKS for the help! I checked with our IT Support and was able to get a backup copy....with a few changes I should be back on track but it would be nice to know what happened. It seem like it is between a run mode configuration and an .exe.  Any other ideas would be appreciated.

THANKS!

Alma

[JÞB]

That vi seams to be a support file inside a build.  Likely a source distrubution!

Block diagrams are removed by the source developers specifically to prevent other users from editing the vi. 

Short answer: you don't have editable source code.

[momof4]

Hum?  Not sure how that would have happened.  Is there a way to back out of that?

[JÞB]

---

@momof4 wrote:

Hum?  Not sure how that would have happened.  Is there a way to back out of that?

---

Rebuild the distrubution and redeploy the build without removing the Block Diagrams-  From the original source code.  Of course, then you risk having code on different systems that do different things- That can lead to "unwanted behavior"-  (What an understatement!)

What are you using for source code control?

Spoiler

The rest of this thead may contain subject matter which evolkes graffically horrorifying images:  Developer discretion is advised

 {EDIT} I I could spell or type I probably would still be stuck programming in some text based language

My command of punctuation sucks too!  All posters are welcome to clairify any posts mangled beyond readability  (But, I'm not the only one to suffer from these things) or ask me what the heck I meant.

[aputman]

---

@JÞB wrote:

---

@momof4 wrote:

Hum?  Not sure how that would have happened.  Is there a way to back out of that?

---

Rebuild the distrubution and redeploy the build without removing the Block Diagrams-  From the original source code.  Of course, then you risk having code on different systems that do different things- That can lead to "unwanted behavior"-  (What an understatement!)

What are you using for source code control?

Spoiler

The rest of this thead may contain subject matter which evolkes graffically horrorifying images:  Developer discretion is advised

---

Spoiler

The response from Jeff is GRAPHICALLY HORRIFYING and EVOKES memories of Spelling 101.  Teacher discretion is advised. 

[crossrulz]

---

@momof4 wrote:

Hum?  Not sure how that would have happened.  Is there a way to back out of that?

---

Run into this all the time with people trying to get really old code converted.  What Happens When I Save My VI and Remove Diagrams?

Summary:  You can't do a darn thing with the VI except run it with LabVIEW 2009.