LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why Doesn't Labview Place New Indicators I create near existing ones on the block diagram?

When I create a new indicator from the block diagram side Labview usually places them way off in space on the front panel instead of near my other existing stuff. I then have to go find them and drag them back to where I can see them using labview's slow border autoscrolling. This is extremely annoying. I would think that after all the revisions of labview with all the intellegent app engineers NI has that something this simple would have been fixed a while ago. Is there a setting I don't know about or something? Doesn't everyone else have the same annoying problem? Help.
---------------------------------
[will work for kudos]
0 Kudos
Message 1 of 7
(2,979 Views)
If you click on the indicator and hold shift-direction key you will scroll five pixels at a time instead of one.  That's the best I can offer.
0 Kudos
Message 2 of 7
(2,967 Views)
you're not the only one.. 😞
 
See this link where we discuss "cosmetic" improvements for future version of Labview:
 
I bring up the subject here:
 
Having a block diagram that spans over more than one screen is not recommended.  So if you're writing the code from scratch, this is normally not an issue.  Just when fixing some other person's code that is WAY too big (spanning many screens on the Block Diagram).
 
LV places the FP objects in relations to position on the block diagram.   So a rule of thumb, both diagrams (Block & Front Panel) should not extend beyond a single computer screen.  Usually the size of the target machine running the software.
 
RayR
0 Kudos
Message 3 of 7
(2,956 Views)
What is your LabVIEW version? (This situation is typcally handled much better in newer versions.)
0 Kudos
Message 4 of 7
(2,955 Views)
There is no fix? Are you serious? Hahaha. Just another reason I hate labview as much as I love it.

Anyways, the shift direction button is a great tip. I will definitely be using it. I hope some people high up in the labview app engineers world read and implement your cosmic improvements for labview thread. Their bureaucracy seems worse than NASA's sometimes.

My point is that even though all my other stuff on the front panel is fitting on one screen, near the origin, labview will still put the new indicators/controls way the hell out in space. Its stupid. If they are going to do that at least let the user click and drag the mouse waaaaaay off the window to get the thing to go faster rather than just let them get within pixels of the border before it stops dragging and starts thinking you want must want to click on some other window on your screen. (Photoshop does a good job of this by the way) That should be easier to implement than a more intellegent new-indicator/control-placement algorithm if they are just being lazy about fixing it.

I would think stuff like this would take as high of a priority as fixing crashing errors because annoying stuff like this effects more labview users. All of them.

p.s. RayR, I hope you are just talking about the front panel because I can count on one hand the number of back panels I have made that fit on one screen.
---------------------------------
[will work for kudos]
0 Kudos
Message 5 of 7
(2,933 Views)


rex1030 wrote:

p.s. RayR, I hope you are just talking about the front panel because I can count on one hand the number of back panels I have made that fit on one screen.



This may be your issue.  I've noticed a semi-correlation between block diagram and front panel placements, and if your block diagram is five screens wide, it's not surprising that your indicator is five screens away.
 
And yes, the block diagram should (in most cases) fit on one screen.
0 Kudos
Message 6 of 7
(2,929 Views)


rex1030 wrote:

p.s. RayR, I hope you are just talking about the front panel because I can count on one hand the number of back panels I have made that fit on one screen.


All block diagrams (vi's & sub-vi's) have to fit in one screen.  It's our internal policy.
 
None of my vi's exceed that.  🙂
 
A good idea is to draw a decoration (red box) and all code must fit inside it.  😉


Message Edited by JoeLabView on 06-05-2008 03:28 PM
0 Kudos
Message 7 of 7
(2,919 Views)