dannyt

HI, I am interested if having the Portal link and view, causes any extra support work or maintenance for the Site Administration team. If it does then I can understand the reason for the poll on this, it would only be worth putting back if a substantial number of people used it. However if the View provided by that links does not add to the Admin Teams work, could the few who want it to stay not still have it anyway ? cheers Danny (missing the Portal link )

Hi, I may be going mad this morning but I cannot see the Portal link any more. This was the main view I used on Lava to see what was going down. Is it's removal intentional ? cheers Dannyt

Hi Shaun, I do understand where you are coming form, honest I do. I just think spending the 2 days to script up something that will then save you two weeks over the coming year as you do the same thing again and again is a good think to do. Still I am happy to agree to disagree and I will cease now :-) Danny

Sorry Shaun, but I also totally disagree with you on this. The Scripting Tools are something that will be of use to ALL LabVIEW developers and I strongly encourage all developers to play with them and not be afraid of them. Surly we ALL develop "Tools", in some way, they are the things that on a daily basis make our job of developing a "Product" easier, quicker and in many cases more reliable. When I programmed in C and Perl on Unix I used things like 'grep' and 'awk' and other stuff all the time, I wrote my own scripts that used these basic Unix commands to do things for me that (as I said above) were quicker and more reliable than I could do by hand. Most people who write in text based languages are totally familiar with the concept of knocking up a little script to do some regular task in an automated manor, that is what being a programmer is about. I use LabVIEW to create Production Test Software that we use in manufacturing to test our products. However I use scripting in a number of different ways, I using scripting to help so that I can automatically create LabVIEW executable builds, I use scripting to help auto-generate and populate a LabVIEW function Global we use. This reads some specification files our product engineers generate. I could use scripting to help auto-generate some documentation of our system, the list of possible uses is endless. The LabVIEW IDE can not be deployed but I still find it very useful Dannyt

Sorry if I am suggesting the obvious here, especially to a man of your experience, but is this not an inevitable result based on your previous post about the "No supported languages installed" or have you sorted that one out already ? Dannyt

Hi Select File -> VI Properties menu option, then from the drop down like select the Window Appearance option. I suspect that for your two example VI's the setting is Custom, and in the Customize.. options the buttons you want are disabled. You could either alter the Customize options or maybe just select Default instead. It would generally be a good idea to read the Help covering the "windows Appearance Properties Page" and have a play with the setting on these pages you will find them very useful as time goes on hope this helps Dannyt EDIT Dash beaten by one minute

Do not know why, but this seemed a fun thing to try So I have been playing this this off and on. I now have a VI that toggles the sound mute button, it works fine in edit highlight mode but is a little unpredictable when not highlighted, would need to play around and put a few waits in place. I am sure some LabVIEW purists will come up with a better solution sound_mute_toggle.vi

You just beat me to the punch there Shaun , I was going to say the same thing. As an added extra here is a list of other useful control Panel app names Just remember that you need to type control and then the applet’s name! Accessibility Options access.cpl Add/Remove Programs appwiz.cpl Add Hardware Wizard hdwwiz.cpl Administrative Tools admintools Automatic Updates wuaucpl.cpl Bluetooth Properties bthprops.cpl Control Panel panel Desktop Properties desktop Desktop Appearances Properties color Display Properties desk.cpl Fastfind Properties findfast.cpl Firewall Properties firewall.cpl Fonts Folder fonts Game Controllers joy.cpl Infrared Properties infrared Internet Options inetcpl.cpl iSCSI Initiator iscsicpl.cpl Java Control Panel jpicpl32.cpl Keyboard Properties main.cpl keyboard Licensing Mode liccpa.cpl Mouse Properties main.cpl Network Connections ncpa.cpl Network Setup Wizard netsetup.cpl ODBC Properties odbccp32.cpl Power Options powercfg.cpl Printers Folder printers Regional and Language Options intl.cpl Scanners and Camera Properties sticpl.cpl Schedule Tasks schedtasks Sound and Audio Devices mmsys.cpl Stored Passwords keymgr.cpl System Properties sysdm.cpl Telephone and Modem Properties telephon.cpl Time and Date Settings timedate.cpl User Accounts nusrmgr.cpl User Accounts Advances userpasswords2 User Passwords userpasswords Windows Security Center wscui.cpl Wireless Link irprops.cpl

Oh you must have a post up for that one , I really know how you feel. I think it would be a great event to be at, but hell do you think LabVIEW 2011 will be a revolutionary as 2010 ? Hell I cannot even join in with the "Summer of LabVIEW" Webcasts being run in the UK as for some reason I am unable to join the events, event though I can watch on demand and all the "test you connection" stuff passes OK. Dannyt

Hi, It is always worth putting a small snippet of code with your questions, just help people see what you are really after. You need to look at the Format Date / Time String Vi on the Timing Pallet, this will allow you to format a Time Stamp input in whatever format you want, 24 hour clock or 12 hour clock with or without an AM / PM addition From the LabVIEW help Format Date/Time String Format Date/Time String Displays a time stamp value or a numeric value as time in the format you specify using time format codes. Time format codes include the following: %a (abbreviated weekday name), %b (abbreviated month name), %c (locale-specific date/time), %d (day of month), %H (hour, 24-hour clock), %I (hour, 12-hour clock), %m (month number), %M (minute), %p (a.m./p.m. flag), %S (second), %x (locale-specific date), %X (locale-specific time), %y (year within century), %Y (year including century), and %<digit>u (fractional seconds with <digit> precision). hope this helps, if you want an example just ask Dannyt

Hi I was looking in the Toolkit list and I could not see and entry for the internet Toolkit, am I just missing it or is it no longer supported ? cheers Dannyt OK I found a link to it toolkits for eval

HI Just added you some Kudos for the comment above. If you post it into the Idea Exchange, I would vote it up cheers Danny

Jim, It can never be said you are one to undersell :-)

Simple idea that would help me Close Other VI's

No much more to say than the title really. Many thanks for the upgrade cheers Danny

Hi Norm I have found this API SO useful over the last week so much Kudos to you sir . Can I just ask a couple more questions. Why all these VI's are Reentrent ? Is there a fundamental reason for this or just your choice. I am just trying to increase my understanding. I can understand that "Get All.VI" needs to be as you do a recursive call on it, but I do not really understand why all the other are. In fact I wonder if you really want things like Item Add.vi to be reentrent. Along the same lines I assume that Debugging is disabled because the VI's are Reentrent ? Finally in the "Get All.vi" which is Reenternet I noticed it calls the "Merge Errors.vi" which is itself not Reentrent, should this really be replaced ? cheers Dannyt

example BOM file -------------- ClearCase Build Info (Build Start) ----------------- ClearCase Build View : petes-dev-ats-814 ClearCase Config Spec : element * CHECKEDOUT element * /main/dev-ats-814/LATEST element * /main/B591-ATS-2009NOV24 -mkbranch dev-ats-814 element * /main/0 -mkbranch dev-ats-814 create_message_event.vi,P:\testTeam\ATS\Projects\test_exec_framework\user_events\create_message_event.vi,\main\1, create_exit_event.vi,P:\testTeam\ATS\Projects\test_exec_framework\user_events\create_exit_event.vi,\main\1, run_sequence_data_type.vi,P:\testTeam\ATS\Projects\test_exec_framework\general_type_defs\run_sequence_data_type.vi,\main\1, update_symbols_run.vi,P:\testTeam\ATS\Projects\Sandpit\update_symbols_run.vi,\main\1, Open File+.vi,C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Utility\file.llb\Open File+.vi,CC PATH NOT FOUND,file.llb kHz-MHz.vi,P:\testTeam\ATS\Projects\Sandpit\kHz-MHz.vi,\main\1, NI_MAPro.lvlib:ma_Check for Equality with Precision.vi,C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\measure\mamon.llb\ma_Check for Equality with Precision.vi,CC PATH NOT FOUND,mamon.llb NI_MAPro.lvlib:ma_Range Check with Precision.vi,C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\measure\mamon.llb\ma_Range Check with Precision.vi,CC PATH NOT FOUND,mamon.llb NI_MAPro.lvlib:ma_Limit Test Outside.vi,C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\measure\mamon.llb\ma_Limit Test Outside.vi,CC PATH NOT FOUND,mamon.llb NI_MAPro.lvlib:ma_Limit Test Inside.vi,C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\measure\mamon.llb\ma_Limit Test Inside.vi,CC PATH NOT FOUND,mamon.llb As you see starts with the ClearCase Config Spec used for the build then lists all the files used in build. Each line is comma separated look like VI name, full filepath, ClearCase extended path info (if a ClearCase object), llb name if VI is in a llb.

Wow sounds like you have set yourself a big but very impressive target Yes a BOM is Build Of Materials, it tend to just be used for a QA satifaction / audit point of view. It can be useful to see easily what files have change between build as it included's the source control system version info for each file. Danny

Hi JG, We do have a automated build system here and have had one for 2 years or so. Until this last month or so it was all based around the openG builder, until I looked at your code and found BuildTargetBuildSpecifications VI. So I have only really used from the code the case for building executables and built my own code around it. On our executables we have a 'Help About' VI that we populate with things like build time, who built it, our ClearCase Configuration Specification and label. So most of the code I have added is my own ClearCase control VI's to check files out, update info and after the build to tidy all this up again. also I create a BOM of my builds. I am really please with the results of this and must pass on my thanks to you in showing my another way to do this. I must admit I am quite sad as I have after about 2 years finally abandoned the OpenG builder. But I have now decreased my build times from well over half an hour to around 5 minutes and my final built executable is around 6M smaller than it used to be. I do as a result loose the OpenG VI rename/ mangle options during build, but as all our software stays internal it was part of the openG builder I never used. Dannyt