Fit block diagram to window

This might be a stupid question, but how do I fit the block diagram of my vi to fill the screen (kind of like a "zoom out" feature)? I want to take a screenshot of my current block diagram in its entirety, but the vi is fairly large. I can't seem to find the option to do this.

You could also use a tool such as discussed in the following thread to save an image of your BD:
http://forums.ni.com/ni/board/message?board.id=170&message.id=124219&query.id=0#M124219
(I beleive there is also a similar thread to show how to add this as a custom tool to the LabVIEW menu.)
Message Edited by altenbach on 06-23-2006 10:02 AM
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Block diagram wont open properly

I have written a big labview program for my application. I have been workig on it for 6 months. I keep adding the peice of code every day and save it with a new name every week.
At one point when I added some code into my program, the block diagram started acting weird and wont let me work on the program easily. For If I add an add function, it would take time and insert this function a couple of inches away where I pionted my cursor. Another issue was that; if I add a while loop or for loop or any other structure it would take time and one added it would add a couple of inches away and expand the main program window (Block Diagram) too.
since then, I started using my company's laptop to develop the code. I have no issues with that lap top till today.
But now when I tranfer this program back to my desk top. It wont open the Block Diagram and wont let me edit it. When I try to open the block diagram. the window appear black out and the LabView stops working.
Is this issure ralted to the graphics of my compute or any thing else? Please help me. Thanks
Mansoor

There is a maximum size that a VI can be. What that exact size is I don't know. It does sound like you have one HUGE VI. If that is the case you really need to think more about using subVIs. It will make your program much easier to maintain and extend.
Also, rather than renaming it once a week you should consider using source code contol. Even if you are the only developer it is a much better way to manage your code. SVN is free and very easy to set up. If you do use source code control make sure you separate the compiled code from the source code. This is an option in the VI properties.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Opening block diagrams directly

The default behaviour for LabVIEW when one double clicks on a subVI in a block diagram is to open its front panel. For a variety of reasons, this is undesirable. Is it possible to open the block diagram directly without having to look at the front panel ?
When you are debugging code, the default LabVIEW behaviour is, how do I put it, extremely irritating ?

Plus, these ideas exist:
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Directly-open-VI-s-block-diagram-from-project-window/i...
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Block-Diagram-default-window/idi-p/972620
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Be-always-able-to-open-block-diagram/idi-p/917601
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-ONLY-the-Block-Diagram-to-be-opened-Without-Fron...

How do I automatically make new front panels and block diagrams a certain size and screen position, like able to fit on a 1024 x 768 screen?

I'm studying for the CLD and I notice that one of the requirements is this:
Develop block diagrams to fit a screen resolution of 1024 x 768.
When I create a new VI, its resolution is slightly too big: 1110 x 768.
When I create a subVI via the menu item Edit >> Create SubVI, it is way too small: 800 x 543.
For both methods of creating new VIs, I would like to specify both the screen position and window size. But if that is not possible in LabVIEW, I'd like a quick way to make this happen. I see some property nodes for VIs where I could write a subVI that could do this for the front panel, but that is awkward. And it does not apply to block diagrams.
Is there a clever way to do these things?

bmihura wrote:
I'm studying for the CLD and I notice that one of the requirements is this:
Develop block diagrams to fit a screen resolution of 1024 x 768.
When I create a new VI, its resolution is slightly too big: 1110 x 768.
When I create a subVI via the menu item Edit >> Create SubVI, it is way too small: 800 x 543.
For both methods of creating new VIs, I would like to specify both the screen position and window size. But if that is not possible in LabVIEW, I'd like a quick way to make this happen. I see some property nodes for VIs where I could write a subVI that could do this for the front panel, but that is awkward. And it does not apply to block diagrams.
Is there a clever way to do these things?
It doesn't mean the default size of the window. It means once your code is complete, your block diagram should be small enough that you can see all your code when its on a monitor of that resolution. Before you test, set your computer monitor resolution to 1024x768. Write your code. If all the code on your block diagram can be seen without scrolling, you will be fine. They won't measure this explicitly. They are basically just saying "you shouldn't have a huge block diagram."
CLA, LabVIEW Versions 2010-2013

Probe windows disappear on Block Diagram

Hi all,
I came across an odd issue yesterday using the probes in Labview 2011. When I attach a probe to a wire and leave the probes inside the probe window they seem to work fine, however as soon as I launch the probes as separate windows, then click the title bar to move it to a convinient place they seem to disapear from the block diagram. Once this happens the probes no longer function and simply retain the values they had before they removed themselves.
I have attached a couple of images to show what I mean:
probe-window.jpg shows everything working as normal with the values in each probe acquired correctly.
separate-window.jpg shows what happens when I launch the probe windows and try and move them. They disappear from the BD and no longer function as probes.
Not a major issue I know but one I find very annoying as I like to move the windows to meaningful positions to clearly tell me which wire the values are coming from on the BD. I couldn't find anything similar on the forum so I don't know if I'm the only one with this problem, but it definitely did used to work!
Any ideas?
Attachments:
probe-window.jpg ‏81 KB
separate-window.jpg ‏98 KB

I can't replicate the condition. Have you tried to run a repair on your LabVIEW installation?
By the way, there is a much simpler way (and more scalable) approach to accomplishing what you are trying to do:
Attachments:
string to array.png ‏18 KB

My scrollbars disappear when resizing my LabView8.6 Block Diagram window

My design can't be seen in it's entirety within the Block Diagram window so I need to use the vertical and horizontal scrollbars to navigate the design. The scrollbars disappear if I resize the Block Diagram window past "some point". If I shrink the window very small, the scrollbars reappear. Other programs I've generated don't seem to have this problem. Any suggestions?

Hi,
Check the scrollbars settings, right click on vertical/horizontal scrollbars and change the settings. If the problem still exists, U can send me ur vi, let me have a look to know the exact problem.
regards
sunil

Labview: Null Window ... stopped at unknown on the block diagram

Hi,
I have a fairly large program that was written in Labview 6.0. Recently we upgraded to Labview 9.0 and this program was exported to an executable with the new version.
When running the executable I sometimes get the following error as seemingly random places. I have not been able to make it crash when not using the executable. Labview: Null Window. The top-level VI ".vi" stopped at unknown on the block diagram of ".vi"
I apologise for having to blank out the vi names but i cannot give vi names, say what the software is used for or give over code. I can say that it uses NI USB 6212 IO cards, interfaces with Rhode and Swartz instruments and uses alot of file IO.
I was hoping that someone could give me a hint on how to debug such an error. I have noticed that When this error occurs, the memory use almost doubles.
Thankyou
James
Solved!
Go to Solution.

I think you open the front panel of a VI that has it's front panel removed during the build. Try to adjust the built settings of that specific VI to include the front panel.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Why does my block diagram change when I copy my code to another system?

I am doing development work on a laptop on Win XP and using LabVIEW 2009 with service pack 1. When I copy the code to the target system, my block diagrams are changed and no longer fit the screen. Much of the code is spread out, mainly down. The target system is running Windows 7 and also has LabVIEW 2009, SP 1.
I notice that any constants that are clusters are expanded when copying the code to the other system. I've gone in and turned off the autosizing for these clusters but they are still expanded. I like to shrink them to a small size for saving space.
I've gone through and manually re-adjusted the block diagram on the target system, but when I copy it back to my development laptop, the same thing happens again. This is not an acceptable way to develop code and it has caused a real problem to proceed. I'm contracting this work and must develop this code offsite. Can anyone please help me with this? I can't keep restructuring my block diagrams every time I copy the code from one system to the other.

Windows XP used Tahoma size 8 as its basic system font. When MS came up with Vista, they changed it to Segoe size 9. I'm not sure what Win 7 is, but I think it is the same as Vista. That font change, and certainly font size change seems to be the underlying cause for block diagrams changing their appearance. (And for front panel controls and labels as well.)
LV seems to use the Windows system font as its default font. Interestingly, it seems like the font sizes in LV are something like size 12, 13, 14, 15. I think a size 9 is equivalent to a size 15, but I'm not sure about the comparisons. (Check out this thread.)
There are a few things you can do to try to make one system look more like the other.
1. Go into the Windows screen settings. In Vista, right click desktop, Personalize. Window color and appearance. Open classic appearance properties. Try changing the color scheme from Windows Aero, to something like Windows Classic or Windows standard. They both use Tahoma 8.
2. Or same as Step 1, but go further into Advanced button. Pick on any option that uses font such as Menu, Message Box, Active or Inactive Title Bar and change the font there. I'm not sure which of the items that has a font setting is the key one.
3. LV uses 3 fonts called Application, System, and Dialog. I think each of those map to one of those Windows options, but I'm not sure which goes to which.
4. In LV, Tools/Options/Environment has a subsection called Fonts. Those 3 basic LV fonts are selectable there. There is also a checkbox for me which is checked and says to use default. If you uncheck that checkbox, a Font Style button becomes enabled. You go in there and you can choose fonts and sizes. And the Application, System, and Dialog fonts as well as all the usual fonts names (Arial, MS Sans Serif, Greek, ....) are selectable along with fonts sizes. Play around in there. The whole section is very confusing, and I have no idea how it works. I recommend going to this idea A better way to specify (default) fonts and putting in a vote. Also this idea, Fix font behavior between windows versions, platforms & executables, deserves some love.
5. Some of these settings can also show up in your LabVIEW.ini file.
FPFont = "0" 15
BDFont = "0" 13 (I think the "0" means app font, "1" means system font, and "2" means dialog font)
Also,
appFont="Tahoma" 13
systemFont="Tahoma" 13
dialogFont="Tahoma" 13
(And if necessary, put these in your built application's .ini file)
As you can see, there are a lot of different things going on and they also seem to conflict with each other. I starting stumbling on the block diagram issue between working on my app on XP at work and on my Vista machine at home about 6 months ago. I think my problem actually started with the front panel when I was trying to align labels, and use some arrow head decals on boolean buttons. I think I did the customization of buttons in a couple different ways (because I did some, came back later to do others, and couldn't remember exactly how I did it.) As a result some decals looked different than others when I changed machines. And I swear going from XP to Vista, or Vista to XP the problem got both worse ways rather than let's say larger one way, and smaller the other way.
Replying to your message is about as much to me trying to combine all the pieces of knowledge I've stumbled across over the past months and year as it is for trying to help you. Hopefully, this information gives you some places you can look at and play with. (I bet #1, would be a quick, easy way to solve your immediate problem, but I haven't really tried it myself to be sure.)
I hope someone from NI who has a better understanding than me about these font issues could jump in and correct any mistakes I made, or add anything I might have left out. What we really need is some sort of "nugget" or National Instruments white paper that really explains all of this in ways we can use rather than us stumbling around in the dark doing things trial and error to figure it out. Generally, any changes to the .ini files require you to shutdown LV and restart it to take effect which can take a couple minutes. And considering all the various combinations of things that can be done above, your talking about dozens of possible restarts, and sending .vi's between two different PC's with two different operating systems, before figuring these things out.

Need to know how to print in one page a big block diagram from labview

Hi!
I wanted to know how i can print a program i made on labview. The problem is that the program is quite big and i need to print it in one page. Just the block diagram.
Thanks!
Meli

Hello Meli,
I know, normaly your VI should not be bigger as the window screnn.
Anyway, you can use the "Print VI documentation" as explain in the following link and and choose the option "Scale block diagram to fit"
link:
Printing Documentation for VIs, Templates, and Objects
Best regards,
Nick_CH

How to add text to the block diagram

How do you add plain text to the block diagram for documentation and can I change the background color to yelllow or something else that may be helpful? see image below
Windows is a 64 bit extension to a 32 bit graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. Byte that Microsoft!
Solved!
Go to Solution.

Just double-click in an emtpy area and start typing. Use the coloring tool to color the text background.
(there is also a "free label" in the decorations palette, but that seems like a detour )
LabVIEW Champion . Do more with less code and in less time .

Can't see block diagram of an auto-running VI

Hello,
I have an old and dirty VI that runs automatically when opened. I cannot see the block diagram because when I stop it, LabVIEW shuts down. There is probably that 'evil' function Stop LabVIEW at the end.
Is there a way to avoid that behavior?
The VI was written a while back in LabVIEW 7.0.
Thanks for the help!
Vincent
Solved!
Go to Solution.

LV_Pro wrote:
One other possible trick to stop the vi without it exiting might be, on Windows machines, to do a "Ctrl ." (holding the CTRL control key while pressing the "period" key)
Not sure there was a "Book X", don't think the Greeks used Roman numerals! ;-)
I have actually seen cases where this doesn't work. Most of the time it happens when in a producer/consumer architecture where the exit logic is not correct and the loop with the event structure exits and the consumer is waiting for something to happen. I was aware of the "Ctrl ." abort but have been forced to kill LabVIEW because the abort wasn't processed.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Can I just open block diagram only

Like I can have only front panel opened. Reason is when I have bunch of VIs
open, I get too many windows to manage even while using 2 monitors. It will
be nice if I can just have the window for block diagram open, if I need the
front panel while editing, I can use Ctrl+E to open it. I know I can
minimize but then all LV windows look same on task bar. Would be nice if
icon of the VI showed up on taskbar buttons of each VI.
vishi

You can use lvwutil/Hide window.vi to hide the front panel.
This method has been around for years.
vishi anand wrote:
> Like I can have only front panel opened. Reason is when I have bunch of VIs
> open, I get too many windows to manage even while using 2 monitors. It will
> be nice if I can just have the window for block diagram open, if I need the
> front panel while editing, I can use Ctrl+E to open it. I know I can
> minimize but then all LV windows look same on task bar. Would be nice if
> icon of the VI showed up on taskbar buttons of each VI.
>
> vishi

Automatically open block diagram on extended monitor?

Hello,
I was wondering if anybody know how to pop-up the block diagram on an extended monitor automatically so that ctrl+E need not be pressed to shift between FP and BD. It would be nice to see FP on monitor 1 and BD on monitor 2(ext). applicable to opening any number of VI/subVIs. (not needing to drag window to ext monitor either)
Thanks in advance,

See page 2 of this thread: http://forums.ni.com/ni/board/message?board.id=170&thread.id=102680&view=by_date_ascending&page=2

Nugget: Open block diagram programatically

There are a way to open a block diagram programatically. Exists a undocumented function located in
"%Program Files%\National Instruments\LabVIEW 8.6\vi.lib\Utility\sysinfo.llb\Set Block Diagram Open.vi"

My good old 7.1. (ok, I run that in hyper-boost mode ) has a property node 'VI.Block Diagram Window.Open'. Should be available for anyone and documented in 2010.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Is Block Diagram Open

Is there a way to tell if the Block Diagram is open when a VI is started? I have a subVI that is set to modal when open. When trouble-shooting, if I run my application, but forget to disable modal for the subVI it causes the system to lock up.
It would be nice if I could set the property of the VI to not be modal if the block diagram was open.
Any suggestions?
Solved!
Go to Solution.

I would attempt this by doing several things:
1) Go to the VI Properties>Window Appearance and click on the Customize button. From there uncheck the "show front panel when called" box.
2) When the VI starts, read the VI Property "Front Panel Window.State" - this will tell you if the window is already openned (ie if the window is openned the window state will be "standard", "Maximized" or "Minimized"). Note: this is the visibility of the front panel, not the block diagram
3a) If the VI is not already opened, set the "Front Panel Window.Behaviour" property to modal and then open the front panel using the VI Invoke Node of "Front Panel.Open". This is basically mimicking the behaviour you describe right now.
3b) If the VI is already opened, set the behaviour property to default or Floating to allow you to click other windows.
4) When finished, if the VI was not already openned, manually close it using the Front Panel.Close invoke node (if it was already openned, leave it openned)
I've attached a screen shot of this kind of thing. I hope this helps,
Shaun
Attachments:
Reading and Changing Front Panel Behaviour.png ‏39 KB

Fit block diagram to window

Similar Messages

Maybe you are looking for