Francois Normandin

That's what "programming" is all about, isn't?

Awesome! Even with no lucky charm sitting close by... I'm sure you'd have nailed it anyway.

Try this one. I set the filter to 1000ms. event_multiple click.vi You'll need to adapt it to multiple controls.

So if I hear you correctly, you mean that the LAVA palette should be restricted to Certified LAVAcr code. Right?

Personally, I would adhere to a package naming convention if it existed. That being said, best practices take time to emerge because best practices have a lot to do with how comfortable people are with a well know concept. Has there been enough water flowing under the VIPM bridge to make it obvious what the best practices are? Probably, but it doesn't mean that everybody "has to" adhere to them to build packages. I think it'd useful to have a few "examples" of how one can name a package, just for the sake of all the occasional package builders out there. Just like design patterns, there are no "one size fits all", but a few helpful recommandations might be in order to get newbies started with a decent naming practice. After all, we've all been beginners at some point and would have liked to find a forum or wiki with a lot of helpful topics... Oh wait, it exists already! The above-mentioned idea to have a LAVAG icon in the palettes to put all the LAVA stuff is gonna have more momentum, I think, simply because it's easy to implement and doesn't mean everyone needs to follow the rule. I wouldn't put my code under a JKI palette because well, I'm no JKI! But a LAVAG palette? Yeah, I'm a LAVA for sure... so it's as good a place to put it as any other.

Hi Vivante, there is no documentation on XNodes because this is unsupported technology from NI. Start by reading about it on the LabVIEW Wiki.

I finally took the CLD exam at NI Week 2010... and passed. Yeepee! A big thanks to all LAVAs for keeping me up to date in my programming style and best practices.

Thanks for the kind words. I hadn't thought of this use case when I put up the Control Generator Tool. I haven't tried, but I suspect that you get a distorted image because the button image you introduce is not the same size and something gets resized. I didn't create these buttons with vectorial images, so they don't resize well. The Hoover effect loss might just be that you customize the button by pasting directly over the "depressed button" and this would overwrite the hoover state. The Vista1 buttons are created from a 6-state system button template (72x72 pixels) and the hoover state is the 4th state (if I remember correctly). So for this to work manually without distortion and keeping the hoover effect, as quickly as possible, you would need to: 1- Create a button with your False state decal. 2- Create a second button with your True state decal. 3- Open the second button with the "Customize Control" editor (the usual Right-click Advanced >> Customize...) 4- Hit the "Switch to Customize Mode" button. Right-click on your button and select one of the depressed state picture (true state). Copy to clipboard. Close this button... you can even delete it from disk. 5- Open the first button with the "Customize Control" editor (the usual Right-click Advanced >> Customize...) 6- Now copy the clipboard image on all three states that represent depressed states. 7- Apply changes and voilà, you have a new True state decal with the same size (no distortion) and with hoover effect. I have made a video but I seem to have a nasty microphone problem and without audio, you might just as well follow the above mentioned steps. Well here it is anyway: <object width="425" height="344"> <param name="movie" value=" <embed src=" type="application/x-shockwave-flash" width="425" height="344"></embed> </object> However, you surely want to do it programmatically. At the moment, it can't be done because the "Preview Control States" VI messes with the button states even if you change them using the Properties VI provided with the API (I'd definitely call that a bug in my implementation). I was able to do the modifications in a few minutes to the existing class. It requires adding a True State Icon, modifying the Read and Write Icon PNG VIs and modifying the Load Icon & Preview Control States VIs. I'll prepare a new version soon and post it here. Stay posted and thanks for the feature suggestion.

Hi Antoine, You MUST have VIPM 2010. VIPM 2010 can now install packages anywhere on disk but it comes at the expense that packages built with 2010 and not readable with earlier versions. Once you move your package to 2010, can't go back. The good news is that anybody can now build unlimited VIs in their packages with the community edition. Some goodies are reserved for Pro edition, but it's gonna open up to a lot of people. Sorry, I guess I should have written this in the readme. (DONE)

It's online. v 1.2.0

You understood it better than me. Now that I read it again (and your answer), I agree with you. Thanks for pointing this out.

The "Parent Class" property requires that you open a reference to your library (refnum, not object), which you can't do at runtime, so RT is excluded too. The Get LV Class from Path primitive works on RT, but the hierarchy can only be found, as stated by AQ in another thread Mike mentioned, through hacking the XML. But this solution has not been posted yet, to my knowledge anyway.

Certainly don't mind... For your RT problem, you might want to keep the hierarchy in a text file. I remember reading about that here on LAVA where people had the same problem. If not mistaken, Antoine Châlons discussed it. (Might be wrong, but try looking for his posts.)

Download VIPM from jki.net. It's a code reuse package manager. Very useful to distribute code, get code from others and keep track of all your own reuse code, with forward portability between versions. If you don't want to install a third-party software, PM me and I'll send you a code example.

HI Mike, take a look at this API. And find attached the latest version* I use. There is code for getting the class hierarchy (array of refs or array of paths). *Disclaimer: This version 2 of the API is not in the Code Repository yet because I haven't ported it back to 8.6 and haven't retested all methods, so use at own risks. But between you and me, the code for hierarchy is safe. I also changed the package naming convention since version 1, so you might get a palette conflict if you have both installed at the same time. It might go back to what it was, but most likely, I'll just change the place where the code is stored and where it's installed in the palette to be able to install both. Version 1 becoming "deprecated" simply because I'd rather call it lavag_lvclass_api than normandinf_lvclass_api... lava_lib_lvclass_api-2.0.0.15.vip

Make a poll? Auto-flagellation is always fun to watch.

Yeah, you were taking way too much bandwidth anyway... No wonder my Garden Inn connection was so sluggish.

It's been in the gallery for a few days now. Although the gallery is not as full as usual. Guess Michael hasn't had time to upload all his stuff yet... Sure was cool to have you around. I still don't have a clear picture of what a cow-orker looks like though.

The Hilton "Garden Inn" is two blocks away from the bigger Hilton. It's 125$ and Internet is included.

Here were the two proposed solutions. I'm sure Rob knew what a 7-segment was, but he just tried another way that could look like it and beat Darren. His way was easier to visualize on the BD, but I agree that it would have been a hard decision on the judges. EDIT: Saw that last post by Darren too late.

Hopefully not some slang that only Chris and Jon will understand... Congrats "mate".

Welcome Dave and congratulations on your CLAD.