crelf

QUOTE(Aristos Queue @ Apr 23 2007, 02:12 AM) You shure gotta a purdy mouth there boy - you use your tongue purdier than a ten dollar whore... (extra credit: name those movies) QUOTE(Tomi Maila @ Apr 22 2007, 06:17 PM) Perhaps the system could require that a few users presses the button... Perhaps what we're all asking for here is (dare I say it?) a rating system for individual posts? (OK Chris, you've said it, now step back and enjoy the show...)

QUOTE(asharma @ Apr 23 2007, 02:26 AM) Glad to hear you're trying, but please don't post a new thread - go back to the original thread and create a new post there (just click on "reply" at the bottom).

QUOTE(asharma @ Apr 22 2007, 09:46 PM) Firstly - IMO that is a pathetic start to a thread - if you want our help, you're going to need to be a lot more descriptive and demonstrate to us that you're at least trying to solve the problem yourself. Your post doesn't even ask a question. What is it that you want? Do you want us to confirm that it doesn't work? If so, what does "doesn't work" mean? Secondly - you've got the indicators in the event cases that you're looking for the event change on - the "value changed" event never fires because the data never gets to the terminal - LabVIEW is a "dataflow" language, and you've achieved what is caled "thread lock". Thirdly, the fact that you did that suggests to me that you're very-much a beginner at LabVIEW, and frankly, that means that LAVA isn't the place for you. LAVA, as the acronym suggests, is for LabVIEW Advanced Virtual Architects - you will be much much more at home and get many more answers to your basic questions over http://forums.ni.com/ni' target="_blank">here. Once you've learned a lot and can proove that you've gotten some experience, you'll be welcomed back to LAVA.

QUOTE(asharma @ Apr 22 2007, 09:46 PM) Firstly - IMO that is a pathetic start to a thread - if you want our help, you're going to need to be a lot more descriptive and demonstrate to us that you're at least trying to solve the problem yourself. Your post doesn't even ask a question. What is it that you want? Do you want us to confirm that it doesn't work? If so, what does "doesn't work" mean? Secondly - you've got the indicators in the event cases that you're looking for the event change on - the "value changed" event never fires because the data never gets to the terminal - LabVIEW is a "dataflow" language, and you've achieved what is caled "thread lock". Thirdly, the fact that you did that suggests to me that you're very-much a beginner at LabVIEW, and frankly, that means that LAVA isn't the place for you. LAVA, as the acronym suggests, is for LabVIEW Advanced Virtual Architects - you will be much much more at home and get many more answers to your basic questions over http://forums.ni.com/ni' target="_blank">here. Once you've learned a lot and can proove that you've gotten some experience, you'll be welcomed back to LAVA.

QUOTE(Tomi Maila @ Apr 22 2007, 06:17 PM) OK - I think I know what you're after now: you want a button that any user could press to suggest to the administrator that the post is somehow inappropriate for the forum that it's in - is that right? We've already got that - it's a button labelled "report" on the lower left side of the post. I figure a flag goes to the admin to check if the post's appropriate and then he/she can do whatever they like with it.

QUOTE(asharma @ Apr 22 2007, 07:47 PM) Are you sure you need this to work in real time? Let's be clear here: real time is a very specific engineering concept that relies on determinism - real time does not necessarily mean real fast. Have a look http://forums.lavag.org/blog/crelfs_technology_articles/index.php?showentry=116' target="_blank">here and let us know if that's what you need.

QUOTE(njkirchner @ Apr 22 2007, 12:16 PM) Brilliant!

QUOTE(yen @ Apr 22 2007, 07:25 AM) Thanks for the info yen :thumbup:

QUOTE(yen @ Apr 22 2007, 05:15 AM) Really? Why?

QUOTE(PJM_labview @ Apr 22 2007, 04:15 AM) I don't. I think you're mixing up the roles and responsibilities of a Premium Member versus an Administrator or Moderator. As a Premium Member myself, I really appreciate the other Premium Members want to get involved - that's excellent, but IMO these abilities should be limited to Admins and Mods only, and not released to Premium Members. That said, maybe what you're actually asking for is Mod status? Maybe ask Mike if you can be a Moderator...

QUOTE(John Rouse @ Apr 22 2007, 03:31 AM) No worries at all John - I just figured it'd get a whole lot more exposure over there.

QUOTE(Pablo Bleyer @ Apr 21 2007, 07:54 AM) Can you please post your code so we can have a look at whay you're doing?

I just wanted to take a moment to thank Stephen for all that he has contributed to LAVA. You have to be one of the highest SNR contributors here, as everything you write is certainly worth reading. In short: thanks so much for being here - I really appreciate it :thumbup: Edit: His name has been added tot he TALM list.

QUOTE(Jim Kring @ Apr 21 2007, 02:51 AM) ...and finale?

QUOTE(Nullllll @ Apr 20 2007, 11:06 PM) You need to learn about smtp in general before you try to implement it in LabVIEW, or any programming language for that matter... As is often suggested to you - do a google search on smtp.

QUOTE(kennoncotton @ Apr 21 2007, 12:33 AM) :thumbup: That's pretty cool - thanks for pointing that out Kennon. QUOTE(kennoncotton @ Apr 21 2007, 12:33 AM) We took it out of the UI in 8.0 because we thought with separate projects people wouldn't run into this as much. We are contemplating putting back in, but for average Joe LabVIEW User it is a little strange to see a GUID like that, even more so to see 2. It's a tough question - maybe you should put it back in and label it "Never never never press this button - unless you really really really have to and you absolutely absolutely absolutely know what you're doing".

QUOTE(Jim Kring @ Apr 18 2007, 03:25 PM) What the...?!? Not bad about 35 seconds from the end...

QUOTE(spacecharly @ Apr 20 2007, 07:40 PM) Yep - that's the way to do it. The config file refnum is a special refnum based on a GOOP repository, and the only way to get to it is the method you used - actually diving into the repository and getting access to the private method. I think that it's a private method for a reason: the config file VIs in vi.llb are meant to be an easy method of getting into the ini files, and encapsulating the file path keeps prying eyes from making changes to the file while the config VIs have got it open, so it's probably not something that should be public by default. As an aside, the use of a repository under the config files VIs is a pretty good place to start if you're new to by-reference GOOP...

QUOTE(gleichman @ Apr 20 2007, 03:52 AM) Thanks for confirming that Alan - I thought I was just overlooking it...

QUOTE(John Rouse @ Apr 20 2007, 03:25 AM) Thanks John, but this isn't the place to put code you want to go into the LAVAcr. Have a look http://forums.lavag.org/index.php?showtopic=3470' target="_blank">here for the submission proceedure.

QUOTE(Stevio @ Apr 20 2007, 01:59 AM) It'd be great if you could post it here so we can all look at it...

QUOTE(LaserDrive @ Apr 20 2007, 02:02 AM) Right- when you create a build, it assigns a tag to it in the *.lvproj file: <Property Name="DistID" Type="Str">{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}</Property> When you try to reinstall that app, the code's already in the registry from a previous app's, so the installer tries to upgrade the app rather than reinstall it. That means that if you have two apps that share the same code, Windows will get confused - you can install the first one okay, but when you try to install the second it'll try to upgrade the first. You used to be able to generate a new code (before LabVIEW 8.20), but I can't see where you do that now... But if you just create a new build for one of the apps then that should solve the problem.

QUOTE(LaserDrive @ Apr 20 2007, 01:38 AM) Are you sure you creating a new installer from scratch, or are you copying an older installer? An installer generates a quasi-random code that is installed in the registry, so when you try to install the same app again (or upgrade it) it knows that it's already installed.

QUOTE(srinivas @ Apr 19 2007, 06:33 PM) Probably, but why would you want to? The "sound output configure.vi" on the palette lets you select a device ID, so you can do it with VIs in vi.llb.

QUOTE(ÜLKÜCÜ_HAREKET @ Apr 19 2007, 05:34 AM) ...then you probably want to look at either LabVIEW DSC, or better yet, Lookout instead of LabVIEW.