crelf

Yeah - that's true.

I never said it was strangers Do you really want to start playing that game? Because, if you do, bring it! ...and that's why I don't think it's a good idea. Because what posts/threads/etc I read is none of your damn business. Maybe what we're looking for is more like tagging? It's like kudos, but with data.

Works fine on my XP.

It's only inappropriate in that it doesn't show enough skin Welcome V - see you at the barbie.

This was discussed here - there's some stuff there that might help. Sounds like you need the VISTA LabVIEW HTML Documentation Generator - it packages your top level and subVIs' documentation into a neat little chm (it can export to html as well). Read more about it here (including a downloadable demo chm file that it generated). Thanks for the plug!

Guys: Admins don't follow every post in every thread, so if you find issues with a thread or post, use the "Report to Moderator" button *on that post*. Then all the admins with get a PM with a link to the actual issue. I suggest that you go back to the posts that have the issues and use the buttons there so we can track them. I'm going to close this thread to new posts.

Yep, you should be fine.

I'm seriously considering having 2 twitter accounts: one for LabVIEW goodness for you geeks to follow and one for what I had for dinner for, well, all the other freaks to follow...

Usage of non-palette VIs is totally great, but I usually ping NI to see if there's anything in the wind about it being replaced (in fact, it's brought up the discussion here about packaging non-palette vi.lib VIs for internal use for a couple of reasons: to expose them to the palette and to ensure that they don't go away/change). Anyway, if you're specifically interested in building stuff around the GEH core, make sure you catch my session on Advanced Error Handling Techniques with LabVIEW at NI-Week - I think you'll like what you see...

Hmmmm - I think I see what you mean. So, for example, you really like a member's posts and you'd like to follow what they think is valuable, you could view what they gave kudos to. I think that could be valuable. I'm not sure if it's doable though.

I don't think it is - for exmaple: I post, then contact ppl directly with a "hey - I think you'll find my post uber interesting" and then they don't kudos it. I supposed that does sound like a bit of a stretch, but this example has actually happened several times to me - someone has skyped/PMed/d tweeted me with a link, I read it and find it less interesting than they thought I would, then they question me on why I didn't give it a thumbs-up (or "thums-up" if you're in India). It sounds a bit out there, but it's a natural process for those who are addicted to getting kudos. When we were designing LAVA 2.0, we toyed with the idea of the kudos system, and there are definately negatives like this, but we figured we needed something better than post count as a status symbol, so we choose to implement it. That said, it's only as accurate as the seriousness in which it is applied and perceived I wonder if we can set up a script that counts the number of posts someone makes on the dark side and automatically decrement the kudos here by that amount... PS: I am, of course, completely kidding. PSS: Or am I? PSSS: Yes, I am.

Just wanted to give everyone a head's up on the direction the presentation is going: yes, there are several layers of error handling, and we could discuss all of those layers for weeks so I've limited my 45 min session to the very core of LabVIEW error processing. I think building error handling modules on top of that core are vital (like several of those already mentioned in this thread) but we need to have a more comprehensive and flexible core first - and that's what I'll be presenting on. I really want this presentation to be a catalyst for further discussion and development of a new core, rather than an authorative lecture (I'll be presenting a couple of core ideas to get the ball rolling, but it certainly won't be a this-is-an-awesome-silver-bullet-that-will-meet-all-your-error-handling-desires presentation - in fact, I don't think either of the 2 paradigms I'm presenting are the answer to replacing the core, but I think they're steps in the right direction). My current plan is to video the presentation and post it here the week following NI-Week, as long as that's okay with NI of course.

"If you're not with us, you're against us". You'll be able to see who didn't kudos, and, by their absence, might consider that negative. Why do you really want to know who voted your post up anyway? I'm not sure I understand why that's important.

Someone created a VI a few years ago that helped you choose color matches (complimentary, contrasting, etc), but I don't remember who it was...

Are they TestStand experts? I'm not sure who moved it, but I'll move it back for you. No need to be cranky - all you have to do is ask. All we're trying to do here is help each other. I think you're right - the reason that you're being constantly told to use TestStand is because, based on your descriptions, the members think that TestStand would be a better way to go. I don't think anyone here has a particular preference to TestStand over LabVIEW per se (as you menetioned, it's primarily a LabVIEW forum), everyone's just trying to help. That said, due to your fierce intent on using LabVIEW over TestStand, irrespective of your motivations, I won't mention TestStand in this thread ever again. As an aside: maybe other members would understand your concept better and not make the mistake of suggesting the-platform-I-promised-not-to-mention-again-in-this-thread if you uploaded a concept diagram or even some architectural code.

Nice try

What? That's not enough for you?!?! Actually, it's about something that's being added that can be applied to VLOOP, but, as Stephen says, you'll have to wait a few more days So, this will make no sense for another week or so: while this technique is certainly cool, it should only be used when appropriate! Just because you can doesn't mean you should. We clear? Good.

To further assist in avoid confusion (or creating more of it), "GOOP" is a registered trademark of the Endevo corporation, and is usually only used when refering to their implementation of by-ref OOP in LabVIEW. I'm not sure if Sciware's "GOOP Developer" actually develops GOOP, or a different LabVIEW OO implementation. There are, of course, many implmentations of OO in LabVIEW: VISTA Class Generator (V I Engineering, Inc - the first OOP implmentation AFAIK) GOOP (Endevo - the real powerhouse in OOP in LabVIEW for many years) LVOOP (NI - the by-val implementation that comes with LabVIEW 8.2 and higher) dqGOOP (DataAct - fast and has little footprint, but I've never tried it for inheritance) OpenGOOP (OpenG - open source implmentation) GOOP Developer (SciWare - never tried it, don't know anything about it) more...? Also, Endevo have OO tools that help you manage your OO in LabVIEW (whether it's LVOOP or GOOP - in fact, the latest version of GOOP is really a by-ref implementation of LVOOP - how cool is that?) with their GOOP toolkit and UML modeller (you can create UML and it will automatically build the classes for you, and vice versa!) I think the next release of LabVIEW might make things even more interesting (if used appropriatley - that'll be the real challenge...)

I'm @crelf

A big thanks to Stephen Mercer from National Instruments for offering up what I think is our very first home-made LAVA/OpenG NI-Week 2009 BBQ door prize: ElectricLAVA Sign Is there anything this guy can't do? From the man who brought us by-val OO in LabVIEW, inspired by LAVA's new logo, now comes the completely custom made LightWire LAVA sign. It'd look perfect hanging over your bar, on the wall of your cube, on the ceiling above your bed, heck - anywhere! This little marvel is 20" wide x 30" high (that's 30cm x 75cm for everyone that lives in a country not stuck to the measurement system that those who inveted have all but abandoned) - so it's big! If that's not enough, Stephen's included a sequence controller that cycles the lights through different colors too! It all runs on 2 AA batteries (hmmm... 3V DC can be pretty dangerous - maybe I should remove this listing from the door prize list and it in my home, for the safety and well-being of all you LAVA members of course...)

I get that a rusty nail relates to scripting (looks more like a spike than a nail), but you want to kill scripting by stabbing it in the heart? Yep, it's a WTF - even with your explination - sorry.

No worries. Let's see: Version 1 of TestStand You started learning it in the tail end of a project You launched into a project without any real training on TestStand itself - only how it related to that project Gee, I can't think of why that'd be a difficult situation Take another look at TestStand - it's come a loooooong way from v1 to v4.2.

Oh crap - I'd completely forgotten about that! Anyone got suggestions on where we could eat? I'm thinking that delicious Thai place on 6th, although I'd prefer it to be something a little more Texan... Maybe we should just grab a table in the exhibition floor lunch area?

Bring it on!

I *could*, but it's actually part of an internal library that does a whole lot of VIPM pre/post build hook stuff, some of which doesn't make business sense for us to distribute. Someday I might release the post-build documentation generator that builds and adds linked chm documentation to all your package files, but that would require me to do some work, and I just don't have time pre-NI-Week. If you remind me in a couple of weeks, I'll have a look at releasing it, as well as some other stuff that supports VIPM package creation... maybe...