BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView vs LabWindows/CVI


@Todd_Lesher wrote:

I know how to use LW. I prefer LV. Try these in both LV and in LW and see how long each takes:

1) Next to the thermometer, add a strip chart that shows the history of the data.

2) Change a numeric display to a gauge with programmable limits.


Can you send you me a charge code? I don't work for free. It'll cost you plenty if you want me to do it in LV. I gave up on LV when I discovered LW.

 

Your first post indicated that manipulating widgets in LW is as difficult as in Qt and wxWindows which is not true, suggesting you had never used LW. I wanted to clear that up, if not for you then for others who may have read your post.

 

 

0 Kudos
Message 181 of 222
(11,378 Views)

It would be faster to make the change in LV than it would be to generate an invoice.

0 Kudos
Message 182 of 222
(11,375 Views)

Hoovahh,

 

Thanks for that great example.  I can code in LV but I prefer LW. In fact I think both graphically and textually (just like the example you provided).

 

But try this:  Print out that page and navigate between the two points.  Try just to follow the map - not all the streets are listed - that would be difficult.  Now use the directions - turn by turn would be easier to follow because it has more detail in the context of where are going and what street names you will see.

 

Now, let me take it a step further.  GPS is the way to go.....  stop....  You are probably now saying, See! Graphical is better!.    If so, hold on there cowboy... GPS could be both,  the graphic part where you watch the map (which is great), or the voice directions (more akin to text) where you don't have to take your eyes off the road (much better).

 

So whenever I use a Googlemap printout to navigate, I tend to follow the text and use the graphical map as only a guide.  But I prefer GPS where I can hear my directions and not use any visual queues or instructions.

 

About the hieroglyphs:  It was more to indicate an archaic language (not so much a bad one).  Did you get the more subtle point that I was making? 

Look at all the symbols and all the pretty colors [laugh].  Frankly, I though I would hear more objection to the pre-school book vs the more scholarly book [smile].

 

Romsky

 

P.S.

I was sent a personal note blasting me about my posts.  Hey, I am just here to stimulate a conversation (which appears to be happening) and to hopefully tell folks not to drink the LabVIEW Kool Aid alone, drink the CVI Punch as well!

 

 

 

 

 

0 Kudos
Message 183 of 222
(11,358 Views)

Use the best tool for the job. Choosing the best tool includes considering the skill set of the team.

Message 184 of 222
(11,348 Views)

I agree.  Most of my teams have been CVI centric, but when I had a couple of LabVIEW centric folks on the team, I of course let them code in LabVIEW. When simple changes are made, the LabVIEW people are slightly faster, but when larger comprehensive changes are made, the LabWindows/CVI people seem to get the job done a little faster.

0 Kudos
Message 185 of 222
(11,344 Views)

@Romsky wrote:

 

About the hieroglyphs:  It was more to indicate an archaic language   

 


...because graphical programming is so old school right?

0 Kudos
Message 186 of 222
(11,320 Views)

My annecdotal evidence points in the other direction.

0 Kudos
Message 187 of 222
(11,319 Views)

Some things are just hard to express with text alone 😄

 

 

 

(...just another one of those flawed analogies ;))

Message 188 of 222
(11,316 Views)

Hoovahh,

 

No, graphical in this sense is not old school, but maybe a step backwards in programming, at least the way LabVIEW does it.  I have used other graphical languages as well (visual HDL for one) which are much eaiser to use.  

 

Altenback,

 

[laughing]  Too funny!  So which one uses more memory to say cat?  You made my day.

 

 

 

0 Kudos
Message 189 of 222
(11,302 Views)

@Romsky wrote:

Someone asked me for a graphical comparisonbetween LabVIEW and LabWindows/CVI.

Attached is something that may help.


Surely there is a better example you could use for the text-language code sample.  That one requires multiple lines of code to do error checking after each actual business-logic step (including a GOTO statement!).   You're inadvertantly making the LabVIEW case.

0 Kudos
Message 190 of 222
(11,293 Views)