New monitors resolution effects on block diagram

I recently got a new PC from IT with quad display outputs.
I got new monitors with different resolutions from the old monitors I was using.
Has anyone noticed when opening old projects on a new display that the block diagram layout becomes a lot different ?
For example, look at the attachment, look how large the "Bundle by name" box is, and how it has consumed all objects around it.
Solved!
Go to Solution.

Did you go from a PC that was running WinXP to Windows 7?
The default system fonts for Windows 7 are a size larger than the WinXP fonts.  And generally LabVIEW uses one of the system defined fonts on the block diagram.  (Also, on the front panel.)  So when you make the change from XP to Win7, everything looks larger, and stuff that was lined up neatly before is no longer lined up and can overlap.
Search the forums for Win7 fonts.  There are several threads that discuss this.  You can add some items to the LabVIEW.ini file to define the block diagram, front panel, and the system, application, and dialog fonts to be related to a specific font rather (such as Tahoma 8 in XP, rather than the windows defined font which changed over to Segoe UI 9 on Windows 7.

Similar Messages

  • New Monitor resolutions problem...

    Hello. I got a Mac G4/466 with a 17" monitor that is going to die... I'm looking for a new monitor TFT. I know Acer, Benq, LG and other 22" Wide monitor supports Macintosh but only in some resolutions like 1152x900 at 75Hz.
    I want to know if there's any problems with this resolutions, and why I can't see the hight resolution: 1680x1050. Also if my ATI Rage 128 Pro with 16 Mb VRAM suppotrs all this monitors.
    Any info will be very acknowledge. Thanks!

    Hi valldeina,
    first of all: WELCOME TO THE DISCUSSIONS!
    The "60Hz" means that the picture refreshes 60 times a second. This is only acceptable on small monitors, on larger monitors you should use at least 85Hz, better 100Hz (this is only valid for CRT-monitors, it does NOT apply to LCDs).
    Both frequency (60Hz) and resolution (e.g. 1024x768) are limited by the video-RAM of your graphic card and, in the case of CRT-monitors, by a hardware restriction by Apple for non-Apple monitors. However, if your graphic card can display higher resolutions and/or frequencies you can by an adapter to activate these (there is just one contact on the VGA plug missing, so if you manage to find out which one that is you can even do it yourself).
    If this answered your question please consider granting some stars: Why reward points?

  • Edit menu control from block diagram

    On my front panel I have a menu control that lists the existing file folders for saving the test data. If the operator want to add a new folder I want the Block diagram to write a new folder and add the entry to the menu control list.

    What I would suggest is that your menu have a selection called "New", then if the user selects this, the file dialog would pop up and allow the selection of a new folder. Using a property node, write the new path to the Strings[] property to update the list. At the end of the program, you could write the list to an ini file to save the new list. You would also want to read this ini file when the program starts and write the list to the Strings[] property.

  • HOW TO RESIZE MONITOR RESOLUTION

    Can anyone tell me if i distribute a cd with a projector on
    it, is it possible to resize the monitor resolution to 800*600
    automatically? and when the projector is closed can i have it
    return the monitor back to the owners previous settings??? Or
    should i just have a note with disc saying 'best viewed at 800*600.
    If it possible to do this in Director Mx can anybody tell me
    how?

    > if i set the projector full screen (800*600), how about
    those computer with different resolution.
    Fullscreen means your projector will play at whatever stage
    size you
    have set. The border around the stage will be at the size of
    the monitor
    resolution (effectively filling the screen - hence the name)
    and with
    the color of your stage background. Try it and see.

  • 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

  • New monitor now screen way off center at proper resolution

    Hi
    After my monitor died I got a 24" LED Combo Television/DVD player FLDC2400 60hz, 1080p resolution by Fluid.  The guy in the shop said it would work as a computer monitor.  The only problem is that when I have it set to the recommended resolution (I clicked on that 'detect' button in the control panel display settings) the image is clear and sharp but waaaaay off to the right, cutting about 1/8 of the display and leaving a thick panel of black over the other side.  If I make the resolution lower it centers again but then everything has that low quality fuzzy bloated look to it.  Is there something I can do so that the proper resolution screen works?
    Thanks!  And if anyone is kind enough to answer please know I am a computer dummy so explain things as you would to a five year old!!! :-)

    Hello @rachel_maria,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I have read your post on how your new monitor displays the desktop screen at an improper screen resolution to the far right. Does this issue occur when connected to a different computer? What is the resolution set for your desktop? I would be happy to help you, but first I would encourage you to post your product number for your computer. Below is a is an HP Support document that will demonstrate how to find your computer's product number. 
    How Do I Find My Model Number or Product Number?
    Please re-post with the necessary information, this way I will be able to research this further for you. I look forward to your reply!
    Cheers!
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • Hi! hooked up my new macbook pro to my LGE2442 monitor using a MDP to HDTV cable and the monitor resolution is terrible. suggestions? thanks!

    hi! hooked up my new macbook pro to my LGE2442 monitor using a MDP to HDTV cable and the monitor resolution is terrible. suggestions? thanks!

    thanks, guys mirror on/off didn't make a difference and there were no resolution options with the cable. switched to a VGA adaptor and all is working great now! cheers

  • 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

  • I need block diagrams for audio processing effects such as echo,flanger,vibrato,chorus for implementing in labview?

    i need block diagrams for audio processing effects such as echo,flanger,vibrato,chorus  for implementing in labview? pls i need it very quickly........

    Hi komalamani,
    i need it very quickly...
    So you better start coding soon!
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • What is the best way to keep the block diagram/ front panel clean?

    Hello,
    I am relatively new to Labview so I'm not able to tell if I'm overcomplicating my programs or making my block diagram too cluttered. I was wondering if there were some ways to tell whether I could simplify my programming just by looking at it (perhaps only experience helps for these things) ? 
    I have attached my VI here. Currently, it has the capability to monitor the voltage and current from two motors. On display, you can see a indicator with the voltage and current values and there are charts toward the bottom that can display waveforms from different motors with a drop down menu. 
    The front panel is rather clean in my novice opinion, but the block diagram seems messy to me, just at first glance. I foresee a problem occuring in the future however. In the future, I will have to scale the VI to monitor 50 motors. All the programming will be the same as the one I have now, except it will have 50 indicators and unfortunately 50 times pretty much everything. I would like to avoid this, but I'm not sure how I could.
    I am using a USB 6009. I am using its four differential inputs to monitor the voltage and current of two motors. In the future, I will be getting more DAQ units (25 total because 2 motors can be monitored for each DAQ). The new DAQs will help will help with more resource space, but I think complicate things with the additional potential of 24 more DAQ Assistants (as used in my code). 
    Thanks for any help you might be able to provide!

    It usually is mainly experience that will teach you the best methods to make your code look pretty. I don't know anyone who is proud of their first from-scratch application. There are a few resources out there to help with best practices, like this group on ni.com, but you'll learn the most from your own development.
    Your front panel looks great. FPs in general are really up to you. You can make it look as ugly or pretty as you want. When you have some duplicate controls and indicator groups, you should utilize clusters and arrays to simplify. You could use a little bit of cleanup in that regard, but not much. Also, personally, I hate reading red text unless it's a warning of some sort.
    Your block diagram could use some cleanup in a modularity sense. You have a lot of repeated code, which you could consolidate in to a subVI that is used in multiple locations, or in a For loop. A general rule of thumb is to keep your block diagram within a single monitor. You shouldn't have to scroll. Your application is pretty simple, so it's hard to mess it up
    Here are some specifics about your block diagram:
    Right click your terminals on the block diagram and uncheck "View As Icon". You're welcome.
    Duplicate operations on each waveform "(x*2-4)/16": create subVI and/or run the waveforms through a For loop.
    You do a lot of 2-element arrays and then indexing. Just replace those with a Select node based on the numeric.
    All of your code is running every time, including your property nodes at the bottom, which is unnecessary. As you learn LabVIEW architectures, you will learn how to bypass this with initialization and exiting code, but for now you should put a case structure around those for only when the motor numbers change.
    I'm not sure how you're timing your main loop, but you should put a delay in there because you don't need the DAQmx node to be pulling as fast as your CPU will allow.
    There are free intro videos you can watch to learn what NI would suggest in terms of coding and teach you some of the basic features and such. Here's a three hour course, and here's a six hour course.

  • Block Diagram Changes from one computer to another.

    When programming in LabVIEW, I generally try to make my block diagrams as neat and orderly as possible. This gives the code a more professional look, as well as making it easier for someone else to quickly understand the program. However, I recently have started doing programming on more than one computer, and have found that my block diagram does not look the same from one computer to another (due to different monitor resolutions). Because of this, the nice, orderly block diagram that I made on one computer looks a bit jumbled on another. Is there any way to fix this, short of standardizing the monitor resolutions on every computer?

    One problem you might encounter is how the application font is rendered on different machines. All text-based diagram nodes (labels, property nodes, globals, locals,...) are affected (grow/shrink) if the font is not the same.
    LabVIEW, C'est LabVIEW

  • LabVIEW exits while editing block diagram unexpectantly

    Hi all, while editing block diagram in LabVIEW 2010, I have experience some strange behaviour from the software. I have two monitors, one has the front panel of main VI and the other - block digram of the specifed VI. When I switch from block diagram to front panel, and vice versa, every now and then the LabVIEW exits unexpectantly without the notice. Upon restarting the program again I get the undo.cpp error. I have attached the error log for my clarification on the type error that I am dealing with. Does anyone have any ideas why this is occuring? Thanks in advance for your help.
    Viktar
    Attachments:
    lvlog2010-09-17-09-35-46.txt ‏2 KB

    Thanks for all the responses. 
    I was using an existing VI as template to create a new program.  There were nested loops in the original program and I needed the logic for the outter loops only for the new program.  After deleting many objects in the 'yes' case in the inner loop, I was left with many loose wires in the 'no' case.  And that's when my problem started, when I was trying to delete them.  Yes, I tried rebooting my PC and that did not help.  The problem seemed to get progressively worse, as crashing started to happen even when I was only selecting a wire.  But somehow I was later able to select one wire, delete it, and did a save.  Then I went to the next wire, and so on.  My program is now cleaned up and I'm ready to go on.  I will experiment more when the problem returns. 
    Thanks again.

  • 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

  • Error cluster constant appears different in two locations on a block diagram

    I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
    The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above.  I have not been able to create someting looking like the image on the left.
    Could someone please confirm what the image on the left is on a blck diagram?
    Thanks,
    Bill
    Solved!
    Go to Solution.

    The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
    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

  • 10.5.2 and Mac Pro monitor resolution issue

    I installed 10.5.2 this morning from Software Update and it has now defaulted to a resolution that my LCD monitor cannot display. I can't even boot into Open Firmware, to the Mac Pro DVD, or bring up the drive selection screen (holding down Option when booting) as my LCD continues to say that it cannot support the resolution of the Mac Pro.
    I had the settings set to the native resolution (1280x1024) before installing the 10.5.2 update and had all updates before the 10.5.2 update installed prior to installing it. I have reset the PRAM many times, reset the SMU, and tried connecting the LCD via both VGA (with the converter) and DVI. I plugged in an old CRT monitor and was then able to get into System Preferences but even after setting the LCD to the correct resolution and refresh rate it continues to say it is being sent an unsupported resolution. My LCD is a Samsung monitor but I don't recall the exact model number right now.
    With the CRT monitor I was able to start downloaded the latest graphics update via Software Update but had to leave for work before I could install it and see if that fixed the problem.
    I have seen a number of Mac Book Pro users with an external display problem after updating but was wondering if any Mac Pro users were having this problem or if anyone knows how to fix it. Thank you for your assistance.

    Update: My monitor is a Samsung 913T and is less than 2 years old. I installed the driver update via Software Update but there was no change in behavior. Any CRT monitor I hook up works fine but I don't have another LCD to test. I tried reinstalling the 10.5.2 update but there was no change with that either.
    I am now using Time Machine to roll back my Mac from right before I applied the 10.5.2 update. I doubt this will fix the problem as it seems to be deeper than that but I figured it was worth a try. I'll also be calling AppleCare support on Monday (hopefully they aren't closed for the federal holiday). I am still seeking any help or suggestions on this front. I don't have the money for a new monitor at this time and would really like to get my current LCD working as it was before with 10.5.1.

Maybe you are looking for