LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

2023Q3 Zoom Ctrl+scroll replaces change visible case function

Solved!
Go to solution

Sorry for resurrecting this, but I was just searching for the same topic!

 

@crossrulz wrote:

I'm of the opinion that there are too many environment options already.  Let's not add more for things like this.


I don't meant to be argumentative, but have you seen how configurable CAD software can be in terms of editor setup? Pretty much everything can be changed, from what all mouse buttons do on click, on click and hold, double click etc etc. I'm not saying the LabVIEW IDE needs to be that configurable, but I think there's a valid argument for it being more configurable than it is currently - especially as it's the kind of software people can spend their entire working weeks in.

 

 

This change for me basically prioritises the ease of one function over the other; zooming over scrolling. IMO, it should be the other way around, especially since zooming should be of limited use to anyone that's following good practices.

Message 11 of 23
(1,740 Views)

I could imagine both using Ctrl+Mouse wheel but it's context sensitive, if inside a case, scroll cases, else zoom.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 12 of 23
(1,718 Views)

@Yamaeda wrote:

I could imagine both using Ctrl+Mouse wheel but it's context sensitive, if inside a case, scroll cases, else zoom.


That will lead to: "why can't I zoom sometimes" type of questions and irritations. 

 

Certified LabVIEW Architect
Message 13 of 23
(1,714 Views)

@thols wrote:

@Yamaeda wrote:

I could imagine both using Ctrl+Mouse wheel but it's context sensitive, if inside a case, scroll cases, else zoom.


That will lead to: "why can't I zoom sometimes" type of questions and irritations. 

 


True! You can't please all no matter what you do. 🙂

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 14 of 23
(1,696 Views)

I can't wait to to see what kinds of block diagrams we're going to see here in the forums.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 15 of 23
(1,680 Views)

@thols wrote:

@crossrulz wrote:

@thols wrote:

Ctrl+scrollwheel was used to change the visible case in a case structure etc. Now it is used for zooming. I have found that I can use Ctrl+Shift+Scrollwheel to get the old functionality, but:

1. Why replace the functionality? Zoom should be on Ctrl+Shift+Scrollwheel.

2. How can I get the old functionality back?


1. Ctrl+Scrollwheel is a common gesture for zooming among other programs, at least among Microsoft programs.  So this is the natural gesture to a new programmer or those who did not already know the structure scroll shortcut.  The same is true for Ctrl+= and Ctrl+- (zoom in and zoom out respectively).  In LabVIEW, they used to be to change font sizes.  Those are now Ctrl+> and Ctrl+<.  And I use these a lot, so it will be an adjustment for me too.

 

2. No, you cannot get the old way back.  You can adjust your muscle memory.  We all have with other things.  I'm of the opinion that there are too many environment options already.  Let's not add more for things like this.


Makes sense. 


No, it makes no sense.  Why would you design a UI for new people?  They should learn the way the UI works and initially learn there is no zooming in labview, like we all love and have loved for decades.

0 Kudos
Message 16 of 23
(454 Views)

@carlos_camargo wrote:

No, it makes no sense.  Why would you design a UI for new people? 

Yes, it does.

• Because these people are familiar with the UI from other programs and therefore have an easier start with the IDE.

• It makes sense to adopt standards. Nobody builds cars with the accelerator on the left side.

 

If you want to stick with your usual settings, check out this post by wiebe.

Message 17 of 23
(422 Views)

@ThomasHenkel wrote:


• It makes sense to adopt standards. Nobody builds cars with the accelerator on the left side.


Which reminds me of French cars in the 90's, i guess pedal placement was the only thing they followed standards with.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 18 of 23
(383 Views)

@ThomasHenkel wrote:

@carlos_camargo wrote:

No, it makes no sense.  Why would you design a UI for new people? 

Yes, it does.

• Because these people are familiar with the UI from other programs and therefore have an easier start with the IDE.

• It makes sense to adopt standards. Nobody builds cars with the accelerator on the left side.

 

If you want to stick with your usual settings, check out this post by wiebe.


Standards are great!  I love standards, I love that hot water is connected to the left tap and am used to that.

However, some parking brakes are a pull lever, others a push pedal, still others a little servo motor activated by a push button, or a pull activated button.  I would also say that if Nissan suddenly switched from having its brake be a pull lever to a push pedal for the same model car, people would have an issue with that.

 

Suppose that Toyota had always made its cars with the gas pedal on the left and the brake on the right.  This went against standards but people loved Toyota cars and knew what they were in for when they bought it.  They even saw it as a bonus because it made the car a bit less desirable to steal.  Then after 40 years of training its users to press the gas on the  left, suddenly they changed it so that applying the gas requires using the left pedal and a new button on the end of turn signal activator stalk.  Think Toyota users might resent this?  This is what NI\Emerson has done.

0 Kudos
Message 19 of 23
(369 Views)

@carlos_camargo wrote:

  This is what NI\Emerson has done.

Just change the ini-file and keep the old behaviour dude.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 20 of 23
(339 Views)