Cat

Too bad they don't have something that goes the other way. I wonder how well this actually works.

I just realized I'm about to hit 500 posts on LAVA. I would have probably preferred if #500 was a deep treatise on some esoteric feature of LabVIEW that will change the programming world as we know it. But we all know that ain't happening anytime soon. Maybe post #1000... So instead, I would just like to express my heartfelt thanks to all of you here at LAVA. To those of you who have helped me out over the years (and will hopefully not tire of helping me out in the future). To those of you whose irreverent words have made me laugh out loud at some inappropriate times. To those of you who ask questions and make me think outside of my own little programming box. And of course, to the (real) Moderators who keep the Wonderful World of LAVA going. I love all you guyze!! Cat

Yeah, I do have minor concerns about getting used to coding on my x64 monster machine here at home, and then having to yawn my way thru waiting on my little x32 laptop at work. But actually, by the time I get approval to use LV2010/2011 at work, my least common denominator application laptop will probably be x64. See, this is just more proof I'm not a true LV geek. While I may have different versions on different computers, I've never had more than 1 version on a single computer at one time. Or maybe it just shows how anal-retentive I am. Or maybe how easily confused I can get. Good, because when I can't get it to work, you all get to help me figure out why.

Doh. Sorry about that. I just moved the thread...

I am in the very early stages of writing a scripting project that will eventually be running on 32-bit machines. I say "eventually" since I haven't moved to LV2010 at work due to stability issues, so I'm only using it at home. This wasn't a problem until I bought myself a brand-spanking new home computer. 64-bit, of course. So the question is -- can I write all my scripting stuff on my 64-bit home box and run it on my 32-bit work box (when I finally upgrade it to LV2010)? Or should I just dumb-down and run the 32-bit LV2010 on my 64-bit homebox so I can move it to my 32-bit work environment eventually? Looking forward to LV2011.......

I often use non-NI hardware... as long as it comes with LabVIEW drivers.

Ditto. I know this is old-fashioned, but how about a LAVA PO box we can snailmail checks to?

If that's what it takes, I'll make the sacrifice!

That's what I *would* have looked like if I would have joined in the post-post party partying. Now that I know what to expect, hopefully when the next NIWeek rolls around that I can attend, I will be in better shape.

Since the campaign seems to have worked, and this thread seems to have wandered off-topic anyway... every time I go to IE I wonder, "What's the difference between a 'Hot Idea' and a 'New Idea' "? Any guesses from anyone out there? Edit: I get that "New Ideas" is actually a list of *all* ideas (all 69 pages of 'em). So the question is really about how "Hot Ideas" -- also a list of all ideas -- is sorted.

Ack! Not sure how I missed this post, sorry. There weren't that many of us girls, so you'd think we would have run into each other at some point. At my current rate of NIWeek attendance, I should be back in 2025. See you then!

A couple of possibilities... 1) Are you using the default 60000ms timeout setting, or have you hard-coded the number? I've noticed in the past that the TCP functions sometimes ignore default timeout settings. 2) Does the IP you're trying to connect to exist on the network, and is the port looking for connections? If not, hopefully Linux handles that sort of thing more gracefully, but this can definitely tie a Windows machine up.

Good question. The Player is (was) actually more complicated than I need. I don't have to be able to run the code, just look at it. Because it is all about me, after all.

So I was cursing my CD drive again as I was attempting to load some code on it so I could walk over to my dev laptop and see some CR code. Which made me think I needed to submit the concept of a LabVIEW Viewer to the Idea Exchange. But it's already there, more-or-less. So please wander over here and vote for this idea. Various reasons are: Community service: I kinda made a promise to myself to start helping out more on LAVA, but that's hard to do when dealing with code is so painful. Code review: I've really been pushing LV training here. I figure anyone who knows C and has LV Core 1&2 can do code review, something I have been sorely missing. But none of my cow-orkers have LV licenses so they can't look at my code. Try printing out 2500+ vis sometime... Viewing more recent versions: It would be useful to be able to look at LV 2009/2010 code (I haven't yet received permission to upgrade). Vote early! Vote often!

What features in particular are you looking to extract? Why won't using spectra work?

Using the XScale.Range property of the chart will give you the currently displayed range/start val/ etc, you should know your X scale increment value (resolution). If this isn't what you're looking for, why don't you post whatever code you've written already and maybe we can help you more.

I would think that if the furnace was set to 200 and the user wanted it to go to 205, they would just type "205" into the control. But maybe there's no keyboard, or your example was a trivial one compared to the real controls that are being set?

Every time I read the title of this thread, all I can think is, "We can't even standardize on how to spell standardise."

I'm in the midst of writing code to use scripting to crawl thru huge C header files and create LabVIEW clusters out of all the structures. (If I ever get time to finish it) This will save me loads of time every time those C header files get changed.

Woo-hoo!! Congrats!

I'm thinking a light that goes red as soon as any change has been made to any control. It doesn't go green until a message gets sent. Visual cues are great things in a UI. But I like the email to the supervisor idea.