Michael Aivaliotis

If you set fit control to pane on the tab control, then only the tab control will resize. Not the contents. One possible solution is to programmatically resize the Image Display control based on the size of the tab control. You would have to put this code in a parallel loop so it always runs and feels smooth to the user.

I'd like to add that you should keep it simple. Animations are nice but not essential. A simple overlay with a message: Updating Graph... or Processing, Please Wait... should suffice. Adding a busy cursor will also re-enforce the message and will prevent clicking on the front panel. Also, don't forget that the busy cursor applies only to the front panel you want it to. In other words, the user will only see a busy cursor on the panel that is busy and he/she can still use the mouse on the non-busy front panels.

No idea how to fix it. But I can try to help you out. I looked at the code. I happened to have the 2400 driver installed because I was using it on a customer project a few months ago. You have a constant and a sweep mode for applying the voltage. Which mode is giving you errors? Have you tried running the Keithley examples that come with the driver? There is one called Keithley 24XX\Examples\Keithley 24XX Read Single.vi There is also another one called: Keithley 24XX\Examples\Keithley 24XX Sweep and Acquire Measurements.vi Try running each one stand-alone without your code in memory and see if it runs without errors. If those run fine then take a closer look at your specific implementation. Also. This is a bit obvious, but I'm not sure of your level of experience, so I'll mention it anyway. You should put breakpoints after each driver call and run your routine. Monitor the instrument behavior after each Driver Vi call. Then track down which specific call generates the error.

I appreciate that link Mark. My daughter is having some issues with 8th grade Algebra.

I swear she's saying: "My titties are OK" Oh, and I think that's a cameo by Jamie from Mythbusters. http://www.youtube.com/watch?v=cWhgBxb16Hs

Thanks for the feedback mje. I've added another package to the list that does not auto-renew.

Ya, but it gets kinda silly when I have to download a 1 Gb driver installer. Don't ya think? I know, I know. You pay for the convenience. But it's still insane.

Noticed this on twitter today: http://twitpic.com/2rb1st What do you think?

I've heard many stories myself. I think purchasing stuff is ok. It's the receiving money part that's kinda risky. For me, I always try to transfer money out from Paypal whenever I can and don't keep a perpetual balance with them. I'd like to know what percentage of their millions of users lose their money this way. Must be a nice profit for Paypal. I'm sure Tony Soprano would like to know how to get a piece of that action!

More details here: http://decibel.ni.com/content/groups/coding-challenge-2010 Let's get someone from LAVA to win this!

The typo was on purpose to see if anyone would notice. It worked!

We need more votes. I'd like to see this idea reach 300 kudos.

This is a call out to all LAVA members. Please go and vote up (kudo) the following LabVIEW Idea Exchange ideas: Create a proper connector pane when doing Edit -> Create subVI Edit >> Create SubVI: Tweaks Provide a way to define the default connector pane Go here to read why: Do you wish "Create SubVI From Selection" worked better? Let's show our strength to help fix a feature in LabVIEW that has been broken since inception. It would be awesome to generate so much community support that it would cause NI to take notice and fix this. Darren and Stephen our asking for our support so let's help them push this through with the power that we have. Please twitter this. Post it on your Facebook wall, do whatever it takes to get it noticed. If you have a blog, then blog about it.

I think NI should offer a discount to female attendees.

That's exactly what I'm saying.

Everyone of course is free to use their own company name (or given name) as a category which goes without saying. But I'm saying it anyway. However a nice guideline would be to use the LAVA category as the main category and then you can put your branded category as a sub-palette of that if you like. The LAVA brand means something. We have an approval process and as time goes on we will be tightening this slightly. Possibly incorporating some of the LabVIEW Tools Network requirements as they apply to us. Being able to package your stuff and get approval to put your code underneath a LAVA palette category is special and is something everyone should be trying to do. Let's all keep working on moving forward.

I really like that icon. I vote we use that as the palette category icon.