LabView vs LabWindows/CVI

[Romsky]

Jeff,

This is Romsky (dubbed the CVI Tripod - I guess due to me being and also having a very large e-peen) [smirk].

You can bold text if you want to with me to make a highlite, but everyone else might think you are yelling [smile].

No need to spell check it, if it is close it should suffice, this is an informal place after all. I rarely spell check here as you can tell.

No, I think graphically too. When in deep thought images pop up (a lot like transparencies) but I can't do that anymore when I drive.  So when I write code when I drive I now do it in text (more like a small horizontal window in the bottom of my field of vision).

I wish I could draw you a picture but that would take too long, so I guess you can take these few dozen words as a down payment [chuckle].

I am biased too, so I am cool with that. 

We pretty much gave up on the left/right side of the brain thing here because it was not factual enough for our discussions.

I didn't want to imply it was all left/or right, it was just poor analogy.  But based on your response...

Interesting fact: People how have had their corpus coliseum severed are shown an orange with one eye shut, they can tell you it's color (orange), but they can't tell you the name of the fruit (an orange), then when the other eye is opened the connection is made and they can tell you both - for the most part there are differecnes in the way both hemispheres process input and output.  So lets all continue to use both sides of our brains.

Hey by the way, is there such a thing as a LabWindows/CVI Champion shield?  I have not seen any.  I am sure there are but maybe they don't get that kind of recognition they desreve from NI.

I liked your opinions, thanks for chiming in!  

[Intaris]

---

@Romsky wrote:

Interesting fact: People how have had their corpus coliseum severed are shown an orange with one eye shut, they can tell you it's color (orange), but they can't tell you the name of the fruit (an orange), then when the other eye is opened the connection is made and they can tell you both - for the most part there are differecnes in the way both hemispheres process input and output.  So lets all continue to use both sides of our brains.

---

Nobody disputes that we use both sides of our brain.  The condition you mention is simply a defect leading to impaired communication between both halves of the brain.  This affects lots of different functions and is simply an indication that the brain requires BOTH sides working in tandem to do many functions we take for granted on a day-to-day basis.  Although there is specialisation on either side of the brain, normal cognitive actions on most everyday things will actively involve both sides of the brain, thus making the plea to continue using both sides of our brains kind of pointless.  One has no CHOICE in the slightest in which side of the brain is used.

I recommend you google Sapolsky.  There's a multi-levture video series available online on the structure and functioning of the brain.

[Romsky]

Intaras,

Always a pleasure hearing from you. 

I agree, this is why we dropped the brain thing. But Jeff brought it up so I had a comment - which kind of showed why we need both sides, albeit in an interseting way.  True we don't choose which side we use or both, but the way our brains have developed, which sections of the brain "fire" depends mostly on the type of input it receives (its not our choice).

Oh well, we are back on the brain thing again.

Hey, wouldn't it be interesting to see how the brain "fires" as one uses LabVIEW and how it "fires" when using LabWindows/CVI?  That would be something.  I'll bet it would not be similar.

Anyway, we all agree to keep using both sides of our brain, savvy?

Thanks,

Romsky

[Romsky]

CORRECTION

[I spelled your name incorrectly] "Intaris", correct?

and "We all agree to just keeping using our whole brain, but we cannot choose otherwise".

[Intaris]

---

@Romsky wrote:

and "We all agree to just keeping using our whole brain, but we cannot choose otherwise".

---

I just have a pet peeve with people promising things or agreeing on things over which they have no control.  A few bad bosses has led me to have an instant urge to react violently to things like that because I've been left to clean up the mess on a few occasions by someone making stupid claims / promises / agreements which quite honestly were never even close to being under their control.

Spoiler

Even if someone has the communications pathway between both brain halves severed (as you have mentioned earlier) they are still using both sides of their brain, the two sides just aren't communicating as they should.  Disclaimer: I have recently watched the full series on humen behavioural biology (a lot of which focusses on how the different parts of the brain interact and what kind of disruptions lead to which types of behaviour) I mentioned before by Prof. Sapolsky at Stanford.

[Romsky]

I have been in the same situations (cleaning up a mess based on someones bad promises and such), I hear you. I think you are taking my comment a little too literally [sincere smile]. I am not trying to control anything, it was more like saying "we all agree to disagree" and move on - not being very serious about it.  But I guess you might have a pet peeve with that because it sounds like we all promise to do something or the word "agree" is striking a cord.  Ok, that is just the way you are, and I now understand you a bit more. If we were all in the same room maybe (just maybe) you would have picked up that my comments were more light hearted and less assuming control. When in a room with my colleagues and the conversation gets to a point like this, I often say something like, "so, we all agree to disagree" and we move on. So, I am interested, when in a similar situation, how do you try to get the group to move back onto subject. This way I can avoid your pet peeves in future, I don't want to upset you.

Here is another I use, "How about those Yankees, I think they are going to do it this year" even if they were in last place in the playoffs. See, a litte joke to keep it light, that's all.

Are we cool?

So I say the following to the forum (group):

Hey, how about that LabVIEW, I think it will totally replace CVI someday.

[Romsky]

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

Attached is something that may help.

[querty999]

---

@Todd_Lesher wrote:

I really like how easy it is to write code in Python and in C. I do not like how long it takes to create and change UI elements in Qt or wxWidgets or visual C. LV front panels are so quick and easy to write and to change without the overhead of the text-based language hooks.

---

Todd,

Modifying UI elements in LabWINDOWS is nothing like modifying UI elements (widgets) in Qt or wxWidgets. UI elements are created in LW and modified almost exactly like in LV.

To create a control element in LW you right click on the front panel, then select an element from a list and drop it on the panel. LW generates the C code necessary to create or modify the UI widget. CVI also creates a callback function in your C code for each control element you create. You then fill in the C code inside the callback function to achieve the functionality your program requires.

You modify a UI element in LW by right clicking on it. A dialog appears where you make your changes, very much like in LV.

Take a look at the NI document "Getting Started in LabWINDOWS/CVI". It's found on the splash screen that appears when you start CVI. Go through the example given. That's all the documentation I ever needed to become productive in LabWINDOWS. The only other documentation you need is the programming examples that NI provides. They are also available inside the LW programming environment.

You obviously already know how to program in C. If you're using LabVIEW you also know how the NI hardware works (sampling, buffering, etc.) You owe it to yourself to see how well that knowledge applies in CVI.

CVI is NI's best kept secret.

[Hooovahh]

---

@Romsky wrote:

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

Attached is something that may help.

---

BAHHAHAHA.  Yeah I can tell you either don't like LabVIEW for some personal reason, or you don't have much experience with it.  I like this example better, posted earlier in this thread.

http://forums.ni.com/t5/BreakPoint/LabView-vs-LabWindows-CVI/m-p/1315667#M14635

Personally I think hieroglyphs convey alot more information than text.  The fact that you don't understand the language, doesn't make it a bad language.

[Todd_Lesher]

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.