Leaderboard

http://vihart.com/doodling/ I recommend starting with the snakes one. Also, keep your ears open, or you'll miss the fun stuff (such as the curves on a plane vs. the snakes on a plane or the knighted five-point-star snake titled "serpentagram").

Pravin, sorry I don't have an answer for you, but you should look at the IMAQ toolkit which has several functions for character recognition. Others, please, what kind of replies are that? Is that how we react these days to such a question? If you don't want to provide an answer, then don't answer it. Ton

You can relink the Label.Text property by setting the StringID of the "Property Item". However, it seems that there is a bug with writing the Property Item String ID for Text Label... I can change easily the property of the node by giving the correct String ID for any top-level property such as Indicator or KeyFocus, but when I input the string ID of any property that is a child of another property (ex: Label >> Text), then it returns an error. Perhaps I don't do it right, but I presume it has to do with the fact that the "All Supported Properties" doesn't return the children... So a workaround would be to set the Property Node for "Label" (string ID: 6332005) and then add a property node for Text...

You can all send a thank you note to JGCode. He posted a question in the ni.com forums that happened to hit at a moment when nothing was screaming for my attention, and I finally got around to going through the VIs that handle New Accessor and the New Override and removing all the passwords and posting those VIs to the forums. http://decibel.ni.com/content/docs/DOC-13196 http://decibel.ni.com/content/docs/DOC-13195 The first link will get you the files that actually handle creating new VIs within a LV class and scripting the different behaviors for the terminals (including the UI for the New Accessor VI dialog). You'll find a wealth of scripting helper functions in this library. The second link will get you the files that handle updating VI icons when the library icon changes, including the composition of inherited class icons. Open the file "MemberVICreation.lvlib". That's where you should begin your explorations. You'll quickly see the two top level VIs -- one handles new accessors, the other handles new overrides. Remember, with great power comes great responsibility. What do I mean by this? I mean that I'd like someone to finish writing the ElementWrapperRetooler.lvclass for me. :-) It's one of the classes that is now unlocked. That class is the start of a solution to "I have a class X that has another class Y as a private data member. I want to create a new method on X that has the same conpane as a method on Y but with all terminals of type Y replaced with terminals of type X. On the block diagram, I want to unbundle the Y, call Y's method, and if there's an output, put the Y back into my X cluster." This has been requested by many people over the four years since LV was released to accelerate development of the Delegate pattern and similar patterns, but I've never finished writing it. All calls to any of the VIRetooler classes start by calling "MemberVICreation.lvlib:VIRetooler.lvclass:CLSUIP_RetoolVI.vi". Honestly, that should be the only public function in the VIRetooler class and the others should all be protected, but since the classes themselves are private to the MemberVICreation.lvlib, no one on the Language team has worried about setting the access scope correctly on the individual VIs. Have fun. PS: Although the passwords are all removed, the VIs and classes are all private to the MemberVICreation.lvlib. This keeps users from using these VIs on their own diagrams. If you want to use them on your own diagrams, make a copy of this library and make it public. That way when I completely change these VIs in a future version of LV, you're linked against your own copies instead of linked against the ones that ship with LabVIEW. We'll all be happier that way, trust me. :-)