Leaderboard

Hi everyone A couple of weeks ago i had the need to put a small suite of applications i made in the tray area, but the VIs i could find to do this wasn't really very intuitive or was lacking the functions i needed. The solution? Another one of these put-your-LabVIEW-app-in-the-tray toolsets .. but this time, a little better wrapped than the example code you can find on NI's site.. ;-) (no offense) So here it is for you to evaluate .. it's not anything near final, and one can always find a number of small features lacking, but hey..it's event based, and its pretty easy to add more events if ever needed :-) Notes: Code is currently for LV8.6 and requires at least .NET Runtime 2.0, but i know for a fact that it runs on Win7 and LV2010.. Installation: Unpack / Extract contained "Notify Icon" folder into your user.lib and refresh palettes or restart LabVIEW.. Examples: Browse into your user.lib -> Notify Icon palette and drag the "NotifyIcon Class Example" VI to your block diagram (or open it by browsing into the "user.lib\Notify Icon\Example" folder) License: Since i made this code in my sparetime, but planned to be using it at work, i've made arrangements with the grand-old-boss and put a BSD License on it.. Feel free to send me any comments / questions AND bugfixes / error-reports Thanks Stinus Well..since FF4 doesn't want to play nice.. here is the code uploaded using good old IE :-/ Notify Icon.zip

I used yours on a side project last week, and I have some things I'd like to change/add in that one. (I should note that it was very easy to use and worked flawlessly!) The "Register LabVIEW User Events" function outputs an event registration refnum, which makes it impossible to register both NotifyIcon events and other user events on the same event handler. (Good ol' LV doesn't allow additional registration of new strict types on an existing event registration wire, and you can only create one dynamic registration terminal on an event structure so you only get to work with one wire.) So I broke out the user event refnum from your "Initial Event Registration" case and made an indicator from it. This lets me drop my own Register For Events node and wire as many types of user events to it as I like. As I mentioned on the NI Community page, the Disposed event doesn't fire the way I expect. Your proposed solution is to modify the order of things in the "Destroy" VI to call Dispose, then unregister the events, Of course, I'd rather handle event reg/unreg myself as explained in #1, so the real solution may be to have "Destroy" call Dispose, then exit, relying on the client to unregister events himself. The menu for my application had a subset of selections that were mutually exclusive, so they basically had to act like a menu ring. I made a little FGV that wraps your API to provide that behavior for any subset of MenuItems. I've attached it in case you think it should be added to the API. Using the name of the library to namespace the VIs is ghetto. Why not add them to an lvlib? There are few enough that load times and memory bloat won't be an issue. I'd like to see this packaged as a VIP or OGP, instead of an unversioned ZIP file. I could help you get started with that, if you like. Finally, I'd like to see that whatever blend of these two solutions we come up with is distributed on LAVAG with the BSD license, instead of NI Community with NI's very restrictive T&C. All told, this is a great LV interface to some nice .NET functionality, and I'd love to see more things like it out in the world! NotifyIcon Ring.vi NotifyIcon Ring Action.ctl

Someone pointed me to something called Maintainable Software. http://maintainable.com/ Anyone have any experience using their services?

RE: CS terminology Yes those term would help those being tested if they know them but the time the same in writting the question could inhibit the non-CS types. I would like NI to put together an glossery of all CS terms that COULD be used on a CLA exam. It would include all of those phrases that non-CS type may not be familiar with by name. The CLA Glossery would; Be posted as part of the exam prep matial Included in the CLA application Included as part of the exam packet. I feel it would; help the CS types relax about the terminology Aide in prep for the exam Allow non-LV types to get a better picture of what a CLA has to know. I do not feel it would in anyway decrease the effectiveness of the exam. After all, the exam is not a CS terminology exam. Re: What Aristos said about a CLA training rookies. Thank you! Ben

I guess you know that a conditional probe can stop/pause the execution. //Mike

As a measurement guy and the dyslexic mascot I have to ask if the test results are true measurement of a candidates worthiness for CLA or are the number indicative of an artificial value that requires skill other than those required for a CLA. I feel a timed test introduces many other factors that we can not compensate for. Alternatives? THe certification can be turned into a project. Candidate gets exam spec days ahead of time to allow them to review and think about. They should also be able to submit interogatory Q's to get the spec clarified (I was confused by more than one spce in the exams that were not clear to me). These interogatories would play a part in the evaluation since good questions are part of what a CLA really has to do. The CLA could generate diagrams to doc their design and submit same. If the CLA candidate chooses to use tool-kits or re-use code, they would submit copies of these tool-kits prior to the exam. On the day of the exam the Candidate would dial-in for a web-Ex to present the design and answer questions. So no time limits and no coding. Just my two cents, Ben And re-certification changes as well! Every five years the re-cert candidate will submit code examples of projects developed since cretification. The Exam would be a casual review to ensure the candidate still works with LV. All of the interesting stuff learned by the Examiner should be documented and fed back to NI training so that the loop closes and teh entire LV world "is better for this..."* Ben * From The Unreachabel Star, Man of La Mancha