Growing block diagram objects

Recall that with objects on the Front panel, one can select and move them in very small increments by using the control arrow keys.
Is there a way on the block diagram to grow a control/indicator with that same granularity and in a similar fashion?  For example, I have  picture box that I'm inserting a bitmap into.  I want to grow the box width by a miniscule amount, but the normal way of grabbing the sizing handle and dragging it doesn't offer me the desired granularity, as it grows to the next grid line.

... or simply hit the letter "g" (for "grid") while resizing, and it will no longer snap to the grid during the current sizing operation.
No need to change the default behavior.
(g is a toggle, so hitting it twice (or any event count) would re-enable "snap to grid")
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • LabVIEW MilliSecs support manager function and Tick Count block diagram object

    Is the output of the support manager function MilliSecs (used in a CIN) directly comparable with the time returned by the Tick Count (ms) block diagram object? i.e. if they have the same value then it is the 'same' time allowing for OS specific time resolution

    > Is the output of the support manager function MilliSecs (used in a
    > CIN) directly comparable with the time returned by the Tick Count (ms)
    > block diagram object? i.e. if they have the same value then it is the
    > 'same' time allowing for OS specific time resolution
    The LV diagram node is built upon the MilliSecs() function, which is
    built upon various OS specific functions. It is safe to treat them as
    though they are the same function and represent the same clock.
    Greg McKaskle

  • Group block diagram objects

    I'm almost certain this question has been asked before, but my searches are coming up empty-handed.
    Why is it not possible to group objects on the block diagram?  I'm using 8.2.1, so if this has been implemented in a later version, you have permission to slap my wrist and send me to the corner for not paying attention.
    I think I recall the option being discussed in conjunction with the new "block diagram clean-up" feature of 8.6, but I think the general tone of that was that it would be cool to group objects and have them treated as a single object when cleaning up the code.
    I have some code which is generating a lot of user events, and when changing datatype (Typedef) it happens that I need to re-arrange things so that nothing is overlapping.  This is a right royal pain without being able to group the event data constant and the create event node together.......
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

    livermor wrote:
    Has this been achieved yet?
    If you like this idea you should suggest it on the idea exchange board.
    Personally I don't really know how often I would use this, or find it useful but others might.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Bug: Front Panel objects relative position change when placing merge VI onto Block Diagram

    I've posted a bug report on LAVA, here:
    http://forums.lavag.org/Front-Panel-objects-relati​ve-position-change-when-placing-merge-VI-onto-Bloc​...
    If someone at NI can reproduce, can I please get a CAR #?
    Thanks,
    -Jim
    Solved!
    Go to Solution.

    Donovan B wrote:
    Hi Jim,
    After my previous post, I also saw this behavior, so I decided to do another test.  If there are no decorations in the VI set to “Merge VI” (“Place VI Contents” for LabVIEW 8.5 and later) the controls and indicators are still not selected when dropping the VI from the Functions palette.  I checked this behavior back to LabVIEW 7.1 and it is consistent throughout that controls and indicators are not selected.  (Consequently, so is the fact that when decorations are present they don’t maintain the relative position).
    I am not sure if this would be better suited as a CAR or product suggestion since it has been this way that long, but it does not appear to be related to the fact that decorations are present in the Merge VI.  It does seem strange that the decorations are selected though.  Looks like the best way to work around this is to drop the VI from the Controls palette.  Hopefully, it’s not too much of a hassle.
    Hi  Donovan,
    Thanks for checking in.
    >  I checked this behavior back to LabVIEW 7.1 and it
    is consistent throughout that controls and indicators are not
    selected.  (Consequently, so is the fact that when decorations are
    present they don’t maintain the relative position).
    This just means that not many people use this feature.  However, now that VIPM Professional makes it so easy to edit the palettes, I'm sure that others will start complaining that this doesn't work as they expect.
    > I am not sure if this would be better suited as a CAR or product suggestion
    since it has been this way that long, but it does not appear to be
    related to the fact that decorations are present in the Merge VI.
     Just look up the functional specifications for this feature and see if all objects are supposed to be selected.
    But seriously, is there a reason that only the FP decorations are selected?  Surely this would be documented somewhere, if there was a good reason for this current (IMO, buggy) behavior.
    > It
    does seem strange that the decorations are selected though.  Looks like
    the best way to work around this is to drop the VI from the Controls
    palette.  Hopefully, it’s not too much of a hassle.
    That's not a reasonably work-around, IMO.  It doesn't make sense to drop Block Diagram components onto the Front Panel.  For example, this bug affects the JKI State Machine.  It doesn't make sense to drop a State Machine onto the Front Panel.
    So, I'd file it as a CAR/bug, and then wait to see how LV R&D feels about it.  If they can find some valid reason for why Controls and Indicators shouldn't be selected, then that's fine (and hopefully someone will explain it to me).
    Thanks,
    -Jim

  • Missing objects - block diagram

    Hello!
    So... My program it's working fine, but it seems that I cannot see some objects in the block diagram (see the attached image), even if they're working fine. do you know how to show them? because I would like to change something and I don't know how to do that!
    I've seen also that if I try to run the clean up diagram function for the whole program labview crashes!
    I'm working with labview 2010.
    thanks!
    bye!

    I'm sorry, I forgot to attach the file! Here in this image you can see how it appears (left) and how it should be (right)!
    Thanks!
    Bye!
    Attachments:
    Image.JPG ‏87 KB

  • Minimizing block diagram space

    Hey all,
    I made an application using LABVIEW which includes a number of while loops, case strucutures and so on. Well, the prob is when i made the application I made big loops in order to avoid confusion. But now since the application is complete, in order to see the entire block diagram ( even with the highest resolution),  I have to traverse a lot, since there is lot of empty space in most of the loops. So I wanted to ask, is there any feature of LABVIEW which helps us eliminate empty spaces in the block diagram without affecting the other parts....
    Thanks
    Khanjan

    Hi Khanjan,
    Although it may require a fair amount of manual manipulation, we do have some tools available to help with the process.  In terms of reducing the size of individual structures, the size is limited by the placement of functions and terminals within the structure.  You can choose to deselect "Auto-Grow" on a specific structure in order to shrink it without moving its contents.  Unfortunately, this will simply overlap the functions, so you will not be able to see some of your code.
    The ideal approach would be to rearrange the elements within each structure.  You can do this by highlighting and moving chunks of code.  In addition, the alignment and distribute objects functions in the toolbar are useful.  Specifically, you can highlight a number of elements and select Vertical or Horizontal Compress in order to reduce the space they occupy.
    Regards,
    Lauren
    Applications Engineering
    National Instruments

  • Seemingly random node placement on block diagram

    When I create an indicator on the front panel, the block diagram node shows up in a seemingly random place. Sometimes it gets hidden. The opposite happens when I create a node on the block diagram. The front panel object placement seems random. 
    Is there a way to get a container where all things will appear in this box? Can I anticipate where something might show up? 
    Solved!
    Go to Solution.

    RavensFan wroteThough finding the origin on the block diagram isn't that easy.)
    Sure it is...Reset Origin
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Examining block diagram- ports on VI- How do I determine which port is wired

    Trying to figure out how a block diagram is wired with a a vi that has lots of ports.  Is there a way that I can identify where the wire goes on the vi? 

    As tst said, you can triple click to see the entire wire.  Some people don't wire properly, with wires going underneath objects.  If you look closely at the attached picture, you can see the highlited wire (the one surrounded by dash lines) goes to the top right corner of the object it is wire to.
    Message Edited by tbob on 08-21-2008 12:30 PM
    - tbob
    Inventor of the WORM Global
    Attachments:
    Wire.PNG ‏8 KB

  • Terminal images for arrays on block diagram

    I had always know that the thickness of the wire is representative of the size of the array on the block diagram (Thin wire, scalar, thicker wires, larger dimension arrays)
    I never noticed before that the terminal on the block diagram contained the [ ] symbols to indicate it is an array.  But also, the larger the dimension of the array, the thicker the brackets are, up to about 5-D.  (Probably because I rarely need a 3-D array, and large than isn't any practical, logical reason for a 4-D or larger array.)
    However, looking at the image of the terminal, the shaded area containing the outgoing or incoming triangle actually obscures one bracket or the other.
    While I wouldn't want the terminal to get any larger (which is why I don't like the icon view, it is way too large), it seems like the terminal should show both the opening and closing brackets to indicate an array rather than obscuring one.
    Any comments?
    Message Edited by Ravens Fan on 08-22-2009 12:59 AM
    Attachments:
    Example_VI_BD.png ‏3 KB

    Definitely keep the arrows. They are what tell me the direction of the terminals.
    As I was saying in another post, there is nothing intuitive about the thick border/thin border differences to tell whether the terminal is a source or sink. I like that they are a bit different, but if you put them side by side with no wires and no arrows, I couldn't tell you which was which.
    As for array size, as Christian says, if I want to know the type/dimensions of the array, I'll use context help. I just thought it was interesting (and I had never noticed it before) that the array size was encoded in the image as well.
    I myself wouldn't mind if the terminal grew 2 or 4 pixels wider, but I can completely understand how it would bother a lot of people.
    I think in the current image, too much is obscured by the arrow and its background, even for the scalar type. Actually, why is there a light background behind the arrow at all. That is the real source of the problem. Eliminate the background, and move the arrow over to the edge, and you can see everything without extra shading and without causing the terminal to grow.
    See below:
    1. Terminal size maintained.
    2. Direction arrow maintained, just slightly moved.
    3. Goofy shaded background removed.
    Message Edited by Ravens Fan on 08-22-2009 09:48 PM
    Attachments:
    terminals3.png ‏5 KB

  • Opening VI block diagram engaging remote instrument control

    This is a phenomena that doesn't seem to cause any major functionality issues - but I'm still curious how opening the block
    diagram window of a VI can automatically engage remote control of any
    connected instruments that are powered up - even when the VI itself is
    not running?  The only problem I have with this is if manual control is needed prior to running the VI.
    Has anyone else encountered this issue?

    What, exactly, causes the "REMOTE" indicator on your device to come
    on?  It looks like if you have any VISA resource objects on your
    block diagram and open the block diagram, LabVIEW searches what devices
    are out there.  I would be surprised if your instruments reponds
    to a simple query by going into remote mode, but that may be what's
    happening.  Can you check the manual for your instrument to see
    what commands put the device in the remote state?
    Robert Mortensen
    Software Engineer
    National Instruments

  • 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

  • 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

  • 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.

  • Navigating a complex block diagram

    Hello Guys,
    I already have an existing VI which is very complex with several tabs. The block diagram is pretty huge and i am having difficulties in finding SUB VIs in the block diagram. Clicking on any of the tables in the front panel doesnt take me to block diagram. Does any one ahs any suggestion as of how to traverse through a design.
    Thanks,
    Assad.

    Assad wrote:
    Clicking on any of the tables in the front panel doesnt take me to block diagram.
    Why should it??
    However, you can always right-click on any FP object and select "find terminal", "find local variables", "find property nodes", etc. All these will take you to the right place on the BD.
    LabVIEW Champion . Do more with less code and in less time .

  • Red box Highlighting the entire work area of the Block diagram

    I have a thin red box highlighting the entire work are of the block diagram...I've checked for breakpoints but dont see any. I run the code and after completion the entire work area turns black for a couple seconds and then the red box flashes and the continue button on the tool bar is hightlighted. Any assistance would be great
    tks

    This is indeed a breakpoint.
    You should be able to clear it by selecting your breakpoint tool from the tools palette and clicking outside of your main code area.
    When your breakpoint tool is going to set a breakpoint, the tool is filled in with black. When is is going to clear a breakpoint, it is not filled.
    You can also search for breakpoints from the Edit menu Find function. Click the Select Object icon goto Others and select Breakpoint. This will find all your breakpoints. Sometimes they get set by mistake and you don't know it.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Maybe you are looking for