The Block diagram that cannot be edited...

[MogaRaghu]

The customer wanted to launch the application ( done in LV7 ) with a shortcut from the desktop and when done with it wanted to close all including the LV environment.

So I made the following changes :

1. Made the application to "Run on Open "

2. Connected the while loop Stop button to the "EXIT" function.

3. Saved and started the application.

Presto!! All worked as expected. Except that I no longer was be able to Edit the block diagram !!

Good - I had a copy of the code before the change and survived the nightmare ....

So the moral : Be very clear of what you are doing before you use the EXIT function.

Just though will share the experience, before somebody makes the fatal mistake as above.

( I have now ordered out my copy of the Application Builder, so that I can have my editable code well away from the customer's PC.)

Raghunathan

[Cyril]

Hello,

You can still edit this VI by opening a blank new one,drop the the vi that you wanted to edit as a subvi and opening it from the block diagram of the b;lank one you jsut created...

[EdDickens]

Here's another way to do it.

Create a directory in your LabVIEW x.x directory named 'wizard', and save the attached VI there. If LabVIEW is running, you'll need to restart it, but then in the 'File' menu, you'll have a new selection named "Supress Run on Open...". Select this and you'll get a browse dialog to select the VI to open. It opens it by reference so it will not run.

This is saved in LabVIEW 6.1, but works fine on 7.0 and 7.1.

Ed

[BenBabb]

You can press the "Ctrl" and the "." keys together to stop the code from running. This should let you get back into your wiring diagram.

[MogaRaghu]

---

@BenBabb wrote:
You can press the "Ctrl" and the "." keys together to stop the code from running. This should let you get back into your wiring diagram.

---

Yes it does. But where on earth did you get this key combination ?

Thanks.

Raghunathan

[Dr._Imad]

it has been like that all the time.
The vi has property---execution---allow debugging has to be checked (on by default) for it to work

[NeilR]

Hi

If you open the "Operate" submenu the shortcut "Ctrl+." is next to Stop.
It was news to me too. 🙂

Neil

[BenBabb]

The company I work for purchased two fabs in Belgium. They write all their code in visual basic, they think that LabVIEW is not a good platform to code in. Anyway, I was trying to figure out why their code was not working and recoding it in LabVIEW and just did it by accident. Just trying to multi task to much.

[Roy_F]

--- But where on earth did you get this key combination ?

Online help has a topic called "Keyboard Shortcuts". You might want to give that a quick browse (ctrl-. is there). If you didn't know about ctrl-., I guarantee there are several others you will want to know about as well (e.g. Ctrl-drag a rectangle = Inserts more working space on the front panel or block diagram.).

Also, in online help, Index, enter "Tips" and you'll see several helpful topics, such as Debugging Tips, LabVIEW Environment Tips, etc. If you go to Debugging tips, you'll see the following on topic entry:

"To edit a VI set to run when opened, break one of its subVIs. The VI opens in edit mode because it cannot run with a broken subVI. If the VI has no subVIs, place it into the block diagram of a new VI and double-click."

I filed a problem report to have this documented with the dialog option. Having it documented as a tip is helpful, but not where you needed it.

[MogaRaghu]

Thanks folks for all your replies.

This thread has been quite useful to me and and has opened up many new areas to work efficiently inside LV.

Raghunathan