09-29-2014 02:03 AM
It's rather fun to see all of you using back doors to avoid to front face the main issue. You can always claim that CLA's don't do mistakes, you don't need zooming, I'm incompetent into tweaking NI's source code or else. The simple fact that you can create a diagram larger than the screen, in the first place, is a trap. Labview should then have been limited to one screen area and icons with no more than 8 connectors. It would break old code ? It's bad code anyway, according to your standard, hence requires refactoring, so it's not a big deal.
And yeah, I'm silly, but that's mostly because of this : http://www.youtube.com/watch?v=dQw4w9WgXcQ
09-29-2014 06:28 AM - edited 09-29-2014 06:31 AM
deleted because you really don't want to feed the trolls.
09-29-2014 07:28 AM
@billko wrote:
deleted because you really don't want to feed the trolls.
Lets make this a thing. I'm all for dialog and discussion but at some point it becomes ridiculous and assume you are joking.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-29-2014 07:36 AM
Who ? Me or billko are joking ? Me, I'm 50% serious, 50% pulling your leg, 100% developper : Robocode !
But the fact is, LabView annoys me more, by having to deal with VI placement and wire routing, than a text based language.
Sure traps could be avoided, but why featuring them in the first place ?
09-29-2014 07:45 AM
@Kochise wrote:
Who ? Me or billko are joking ? Me, I'm 50% serious, 50% pulling your leg, 100% developper :
I was refering to you. No one who suggests that a block diagram should be limited to one screen can be serious. How about we limit text to the same limitation, you may only have one screen full of text, no scrolling. I guess that would mean no single text file can be larger than say 10KB.
Also no one who isn't a troll links to that video.
@Kochise wrote:
But the fact is, LabView annoys me more, by having to deal with VI placement and wire routing, than a text based language.
Sure traps could be avoided, but why featuring them in the first place ?
Why support a GOTO it is a trap. Why support a single letter variable name, it is a trap. Why support breaking loops, it is a trap. The more limitations a language puts on a developer, the more likely I am going to hit one of those limits and be annoyed by it. LabVIEW is relativly open as far as letting you shoot your self in the foot. But those features that cause new developers to shoot them selves in the foot, are the features that advanced developers use to make very cool design patterns and frameworks. Don't limit the developer, educate them.
No one said CLAs don't make mistakes, I clearly said not to blindly believe them. I don't know what NI source code you have access too but I've never had the privlage of seeing or editing any.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-29-2014 07:57 AM - edited 09-29-2014 08:00 AM
I don't have access to NI source code.
The video has Rick Rolled you ? That's the fun bit of the Monday morning, hope it drew a smile on your face for the rest of the week 😉
LabView has the sad tendency to open two buttons in the task bar : one for the front face, one for the diagram. More you create of sub-VIs, more you have buttons open in your taskbar, to a point it becomes cumbersome. You open 8 sub-VIs to review and/or edit them, you'll get 16 buttons open. Not to speak about the tools panel, the probe viewer, the contextual help, etc... Like I've told you, developping with LabView requires a completely dedicated computer with at least 3 displays : front face, diagram, tools and panels.
That's why I avoid coding sub-VIs and prefer "huge" diagrams with enumerated loops to simulate sequences. A good event handling and message passing is the key.
And this stupid "always on the top" behavior, select one LabView window bring them all fore front, hidding any other program like documentation or online help...
It's not really trolling, that would have been if I had no valid and solid argument, but really LabView's user interface is so 90's it is sad.
09-29-2014 08:12 AM
Sounds like you need to do some good searching in the Idea Exchange and give some ideas Kudos.
09-29-2014 08:13 AM
We are getting very off topic. If you want to make a new thread about things in LabVIEW that bug you go ahead.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-29-2014 08:18 AM
Hmmm, I bet that I'm surely not the first to get irritated by all these quirks, and yet none of them have been addressed by NI, for various reasons and excuses. So I think it's of little to no use at all.
And for the zoom, hence, you get the idea as well...
09-29-2014 08:55 PM
@Kochise wrote:
Hmmm, I bet that I'm surely not the first to get irritated by all these quirks, and yet none of them have been addressed by NI, for various reasons and excuses. So I think it's of little to no use at all.
And for the zoom, hence, you get the idea as well...
Are you kidding? Of course they listen to suggestions - just look, we have a new icon! 😉