LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Response to Matt Kisler's reply regarding the lack of a labview zoom feature

'I'm sure there are many reasons why a zoom feature hasn't been implemented yet. The one I've heard the most is because there are indeed utilities out there that can be used to zoom. '

The zoom programs that I have found are generic windows programs that simply magnify part of the users screen. A true zoom can implement much more than a simple magnification of one area of the screen. I would like to be able to use the wheel of my mouse and see the whole diagram zoomed in and out analogous to the way internet explorer scrolls up and down when using the wheel.

'A zoom feature is something R&D is working
on so you should see it in an upcoming version of LabVIEW. For the mean time, you can certainly use the 3rd party tools out there. '

I don't really feel that this is a valid excuse for the lack of a zoom feature. Labview has been around a long time and it seems to me, and to everyone I have spoken to with Labview experience, that a zoom feature is obvious and is expected to be in the first release of a graphical program, not delayed until post-Labview6.1. Also, it does not seem terribly complicated. A zoom is something lots and lots of graphical programs (to my knowledge all graphical programs minus labview) implement and with a well designed front end should be rather trivial.

'Something else to always remember is the power of the subVI. The more you can modularize your program into subVIs, the easier your top level application will be to read.'

Now all of us who have programmed enough know of the importance of modularization, but I would also assume that most of us have encountered situations in which this is simply not possible or not the best decision. The former, when you inherit someone else's code and have to "embrace and extend" in a limited time period, the latter when there is some routine that has been properly modularized into segments which still comes out to be rather large (ie a front panel on a large labview program). Even though the panel is simply doling out tasks to subroutines, if the front panel has a large amount of buttons than you end up with a large amount of if/else blocks that handle the button clicks.

Matt, I really appreciate your previous response and I look forward to any additional input.

Nate
0 Kudos
Message 1 of 3
(2,749 Views)
HI Nate,

Since LV 6 and controlref's it has been been possible tomove much of the control related operations into sub-VI's. This goes hand in hand in increasingthe abstraction between the GUI and the lower level functions. Only the VI' that care have to pay attention to the control.

The event structure available in 6.1 also simplifies GUI maintenaces functions.

Now,
If I could only figure out how to configure an event in a sub-VI to trigger froma control on the GUi...

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 3
(2,749 Views)
Hey Ben, thanks for the input, I think it will come in handy. However, it by no way excuses the lack of a very useful and obvious feature on the part of NI.

thanks again,
Nate
0 Kudos
Message 3 of 3
(2,749 Views)