Antoine Chalons

Suneel, I don't know exactly how it works but look, the ACL parameter type is a string (not a string array) so I guess the expected input is the user name as a string and the output will be this user's access rights. See : hope this helps

QUOTE (Suneel @ Sep 12 2008, 01:21 PM) Hello Suneel, I haven't tried it but I guess you have to use the DSC module function, located in DSC Module > Security, there you have functions to get the group list of a domain and the user list of a group. I assume you will have to define domains, groups and users to get it to work. Hope this helps

QUOTE (neB @ Sep 10 2008, 05:24 PM) I don't think so.. the right url will be enough www.ni.com/beta

This one is for Todd

QUOTE (Aristos Queue @ Sep 10 2008, 12:59 AM) The same for me , I am quite demanding with myself about having clean diagrams, one things IMO that could improve the auto diagram clean-up is having wire labels ( ). When I try to clean up a diagram my free texts (code documentation) are often moved in a way that bugs me ; if I could bind my doc texts to wires, I think it would help.

Yes, you are not the only one ! I also went into the process of making core subVIs re-entrant, to helps with this I wrote a small piece of code that checks all the VIs in memory to see if they are re-entrant or not : I agree it would be cool if LabVIEW could automatically add a "re-entrant glyph" on the VI icon, but until this feature comes I do it myself. Hope this helps

QUOTE (Neville D @ Sep 10 2008, 02:01 AM) Great links ! :thumbup: Thank you Neville and Karissap !

Hi all, I saw this article on NI knowledge base dealing with how to get the PXI controller's internal temperature but it is restricted to a 819x and 818x controllers. I have a PXI 8106 and I'd like to monitor it's temperature to be able to disable some intense processing when it gets over a certain value. How to get that in LabVIEW 8.5 :question: Also, I noticed that MAX shows the current temperature for each DAQmx board plugged in the PXI chassis - and yes the temperatures of 2 boards are different - so I guess there will be a way to monitor each DAQmx device's temperature from LabVIEW. Anyone knows how to do that :question: Cross posted

QUOTE (neB @ Sep 9 2008, 12:50 PM) I totally agree with that, you can't seriously ship a system to a customer without some kind of event logger. The time spent on this is saved hundreds of times when you have many system out in the industry !

QUOTE (Ed Dickens @ Sep 4 2008, 02:16 PM) LOL

QUOTE (Ed Dickens @ Sep 3 2008, 07:52 PM) Now that could explain the quote from your daughter :ninja:

QUOTE (PaulG. @ Sep 2 2008, 10:38 PM) I'm sorry it doesn't help... I know how annoying this issue is... Apart from upgrading LabVIEW and working on a USB external hard drive and copying twice a day to the network drive until you can upgrade. I do understand it's a workaround you might not like but that's what I did during 3 month to get ride of the the ducks

QUOTE (PaulG. @ Aug 29 2008, 07:08 PM) Hi there, There is a long http://forums.ni.com/ni/board/message?board.id=170&thread.id=202946' target="_blank">thread on NI forum about that very anoying issue. The issue is even worse on LV 8.5 than in 8.x but fortunately it is fixed in 8.5.1. I know no other solution than upgrading. By the way, if you "save as", and don't change the name, it will ask you if you want to overwrite, say "yes", and most of the time it saves the VI succesfully ; weird.. Hope this helps

QUOTE (crelf @ Aug 28 2008, 06:10 PM) Right, no point... other than hiding the constants, so no real point. Just thinking out loud QUOTE (crelf @ Aug 28 2008, 06:10 PM) sounds like a pretty intense game of Chinese Whispers where language is involved too

QUOTE (crelf @ Aug 28 2008, 04:52 PM) Yes. I assume it's for the same reason that you cannot change the default value of a control at run time. What I was meaning by "the fact that the tags can't be modified is a security, no ?" is that, in a way, being sure that it will not be modified whatever happens can be interesting for storing default values. Often default/last used values are stored into an INI file, what if the operator deletes or moves the INI file ? Well load the default value fron the VI tag you are sure no one will screw the VI tags . This is what I meant by "security". Is there a transparent-babel fish-like animal we could stick into our eye to understand anything written in any form of language ? And what if I stick 42 babel fish into my ears, would it work ?

QUOTE (normandinf @ Aug 22 2008, 08:04 PM) Well... It's not too bad, the fact that the tags can't be modified is a security, no ? I mean.. you can store the default settings into tags and in case the INI has been removed / screwed by someone, then load the default settings from the VI tags, no ?

QUOTE (Darren @ Aug 27 2008, 09:47 PM) Indeed ! I use these : - "alt + space" in LabVIEW for QD - "ctrl + space" for spotlight - "apple + space" for quicksilver

same idea behind : act without doing Ubiquity EDIT : ooops.. just noticed Michael has been a little bit faster than me. Anyway, great minds think alike :thumbup:

QUOTE (crelf @ Aug 27 2008, 12:01 AM) In the end, why people keep saying global warming is bad ??

and i guess it is pointless to ask when such cruise will be organized in Europe :-o

uffffffff... Nice wallnut shell !!!

QUOTE (GaryTan @ Aug 26 2008, 06:24 AM) Hello, To zoom out, select the zoom tool, hold the shit key and clic on the image display. The major drawback of this is that you cannot control the zoom factor accurately. To be more accurate you have to do it with a property node on the image display and use the SGL zoom factor (you can even use different factors on X and Y). Hope this helps

QUOTE (ASTDan @ Aug 21 2008, 04:36 PM) It's the same for me.

QUOTE (vidur moudgil @ Aug 20 2008, 02:20 PM) Here is a quick example in LabVIEW 8.5.1 with comment on the block diagram. Hope this helps

QUOTE (vidur moudgil @ Aug 20 2008, 11:25 AM) Hello, As far as I know you can not create controls/indicators dynamically. What you can do is place all the controls/indicators on the and use property nodes to hide/show only the controls/indicators corresponding to the selected case. Another way is having a tab control, and create one tab per case. I hope this helps.