Jump to content
GregSands

Worst LabVIEW design feature

  

96 members have voted

You do not have permission to vote in this poll, or see the poll results. Please sign in or register to vote in this poll.

Recommended Posts

This is one of my pet peeves too. Along with the amount of coding that must be done just to make a UI work. Most projects I find nowadays are about 60% UI code and 40% real-stuff. The UI hasn't really changed much since the MAC original (in look and feel). No matter what you do. It always "looks" like LabVIEW. I think we would see many "new" looks if NI gave us access to the controls canvas and "onPaint" event..

I'd put that percentage even heavier on the UI side. I honestly can't quantify the effort I put into writing obscure hierarchies of VIs to deal with the oddities features of the LabVIEW controls in an effort to make the UI behave at least somewhat consistent with anything else the user interacts with elsewhere. For anything other than the basic scalar controls, I find it takes all of a few seconds for a user to realize they're not dealing with a "normal" control. Don't get me going on trees or multi-column list boxes...

I develop 100% Windows platform locked applications, and I swear, next time my UI is going to be 100% .NET or WPF based controls, except for the graph objects. The graphs I think are the strongest UI components NI has, and even they are showing their age.

Share this post


Link to post
Share on other sites

:thumbup1:

...although I'm not sure I'm happy about being called an "old timer" :) Seriously though, when it first was released, I resisted, but after forcing myself to use it I wouldn't go back.

After reading this from Chris, I guess I'll now have to spend the time to use and love the Auto-Tool myself. Maybe I need to get a better mouse to be able to position the cursor more precisely.

Yes, I am an old timer, though to be honest my first year at NI I resisted learning LabVIEW at all, having started as a LabWindows/DOS and then CVI guy.

I always (jokingly) tell the guys in my group, that if a feature didn't exist in LV5, I likely do not use it.

Share this post


Link to post
Share on other sites

I'd put that percentage even heavier on the UI side. I honestly can't quantify the effort I put into writing obscure hierarchies of VIs to deal with the oddities features of the LabVIEW controls in an effort to make the UI behave at least somewhat consistent with anything else the user interacts with elsewhere. For anything other than the basic scalar controls, I find it takes all of a few seconds for a user to realize they're not dealing with a "normal" control. Don't get me going on trees or multi-column list boxes...

I develop 100% Windows platform locked applications, and I swear, next time my UI is going to be 100% .NET or WPF based controls, except for the graph objects. The graphs I think are the strongest UI components NI has, and even they are showing their age.

I'm 100% with you here...ESPECIALLY the tree view....frusty.gif. - and my UI are "simple" (or they would/should be...lol). I went through a stage of writing front ends in another language and have only the backend IO and stuff in LV. I didn't find many downsides to this apart from my abhorrence to mixing languages. In fact I might play with it again but using TCPIP as the glue rather than DLL calls. Oooh. Epiphany blink.gif This would mean the UI doesn't even have to be on the same machine biggrin.gif

Share this post


Link to post
Share on other sites

I hate, hate hate hate the new probe windows....

The new Icon editor is next on the list.

I'd like to add a bit more to this so I don't sound harsh. I like the idea of overhauling the probes and the icon editor. It's a step in the right direction. They just both need improvements to make them really useful for me and not get in the way of my workflow. They're not there yet.

Share this post


Link to post
Share on other sites

I'd like to add a bit more to this so I don't sound harsh. I like the idea of overhauling the probes and the icon editor. It's a step in the right direction. They just both need improvements to make them really useful for me and not get in the way of my workflow. They're not there yet.

Nope. I think you were right the first time.biggrin.gif I no longer use the probe window preferring to slap indicators all over the place nono.gif

Share this post


Link to post
Share on other sites

I develop 100% Windows platform locked applications, and I swear, next time my UI is going to be 100% .NET or WPF based controls

Here's some grist for the rumor mill...

Somewhere along the line, possibly when installing LV10, I saw a reference to Microsoft Silverlight. It might have been a EULA. I didn't think too much about it at the time, but at our local user group meeting last week the sales rep mentioned R&D is working on some sort of Silverlight integration for a future Labview release. I'm sure it's at least a couple versions down the road, but it's nice to hear NI is trying to address the UI problems.

Share this post


Link to post
Share on other sites

I don't know about the future of LabVIEW but Silverlight is currently used in MAX and also for configuration of targets via the new web interface. Additionally it is used for the Web Builder UI.

Share this post


Link to post
Share on other sites

Most likely it's as jg mentioned, for the Web Builder UI. Which looks pretty slick I might add.

I'd welcome an overhaul of the UI components, but when they do do it, I'd expect it to still be cross-platform owing to NI's long history of doing as much. This is part of the reason I'm not holding my breath for a set of native feeling controls.

Share this post


Link to post
Share on other sites

I don't know about the future of LabVIEW but Silverlight is currently used in MAX and also for configuration of targets via the new web interface. Additionally it is used for the Web Builder UI.

And it's a long way to be anything but Windows only. I know of Moonlight but sorry guys that is not cutting it yet for use in an application like LabVIEW on non-windows platforms. Even Mono is still lacking quite a few things to be a true .Net replacement.

Share this post


Link to post
Share on other sites

I'm some kind of freak of nature, I like both the auto tool and the new probe window

:blink:

Share this post


Link to post
Share on other sites

The marketing.

It's tiring having to continually defend LV (and therefore my budgets) as a "real" language.

I'm aware that I answer a 1+ year old message, but I totally agree with that.

I have basically learned programming with labVIEW, so I didn't know what a non-programming langage was (I also did quite a bit of c++, which is also a programming language). And back in 2008 I spoke with a PR guy from NI that told me labVIEW was kind of like Matlab. So when people asked me to write them nice programs in Matlab a couple years ago, I joyfuly accepted. That was when I understood what "not a programming language" is. In the end, the situation of LabVIEW is very odd : people who use it think it is not a programming langugage because they don't know what a programming language is ; and people who know also think it's not because NI told them so. Anyway, I know and at least I can thus feel vastly superior to the majority of other humans being, that's one positive point.

Share this post


Link to post
Share on other sites
...at least I can thus feel vastly superior to the majority of other humans being, that's one positive point.

Spoken like a true programmer! :thumbup1:

Share this post


Link to post
Share on other sites

Stupid programmers.

 

Or NI Marketing, it's kind of the same thing.  :yes:

Edited by shoneill

Share this post


Link to post
Share on other sites
The icons. 32x32 pixels on the block diagram? 

I agree but there has to be a limit right?  When LabVIEW was first developed maybe 32x32 was a good size.  Maybe they didn't have very complex sub VIs needing a bunch of inputs and outputs.  

 

If you do want another way to view a subVI you can right click it and choose to un-check View as Icon.  Then you can resize the subVI (dragging down) and your terminals will be displayed in a larger manner.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.