Using Labview 2010, really annoying ¡¡¡ auto grow

[carlosxyz]

Using Labview 2010, really annoying ¡¡¡

I did disable auto grow, After "drawing" my code block diagram runs fine, all the wired, but after run the program, all the wired groooowwww, and the I have a Gcode really large, after try to fix this problem, routing all over again Icons dissapear, all they are there but I can't see them

this is a common problem between community ? or maybe my computer is wrong ¡¡¡ or what ?

I want to share with you my 2 codes, I wish you could help me to fix this:( One of them is in LV2010, another in LV8.6

By the way, in LV8.6 does the same thing ¬¬ I tried to open it even in Mac OS X But it does't work out. 😞

Thanks bye

[altenbach]

Sorry, I don't have the simulation toolkit and get errors opening your VI.

Can you show a picture of before and after?

[carlosxyz]

this is 2 screenshoots, as you can see, the front panel looks fine, even runs fine, but the diagram dissapear jajaj 

[johnsold]

I think your problem is the size of the block diagram.  It is over 18000 pixels wide!!! LV has had problems with any diagram or panel over 16384 pixels.  You may need to start over.  I was unable to salvage enough to be useful.

If you look at the left edge of the sequence frame and compare it to the left edge of a small frame in a new VI, you will see that it is distorted.  If you drag over an area near the left edge you can select several nodes and wires which can be moved by the arrow keys.  There are hints in the way things move that they were distorted by autogrow.

The style guides and most experienced LV programmers recommend:

1.  Keep all panels and diagrams to the size of one screen.  My screen will support structures up to about 1660 pixels wide.

2.  Avoid the use of sequence structures.  They have their places, but those places are rare and should be employed with thorugh understanding of the effects they have on dataflow.

Lynn

[richjoh]

Check all sequence steps for text constants that span larger than the screen display. Some constants controls are populated when you create a constant text box. If a carriage return is not in the block of text, the words span from left to right blowing up your sequence structure.

I second the style guides mentioned above are a way to practice your "style".