Michael Aivaliotis

QUOTE (mesmith @ Feb 5 2009, 01:50 PM)

I passed my CLD

Lucky for me, Michael didn't get to grade my exam - or maybe his advice kept me from making silly mistakes!

Thanks to all for the feedback and help - LAVA is a great community.

Mark

Big congrats to you! And thank you for letting us review your sample program. I think it's good practice to let other LAVA members (or others in general) review your work. This is one of the points mentioned in http://labviewartisan.blogspot.com/2009/01/labview-certification-preparing-for-cld.html' rel='nofollow' target="_blank">Darren's blog post.

QUOTE (Darren @ Feb 3 2009, 10:56 PM)

I just got a new Vista machine at work a few weeks ago. ... (for example, the Start menu took a second to appear with the default Vista theme, but appears instantly with the Classic theme).

-D

Did NI give you an old slow machine? Oh, I see, It's because you program in LabVIEW right? All the C developers get the good stuff.

The start menu shoes up instantly for me.

I've added a feature (extension) to the Wiki to make it easier to add an article to a specific category. It's located at the bottom of the editor and it works with the plain text and rich text editor. It shows you the existing categories assigned (if any) and performs an auto-suggest as you type of existing categories that are used in the Wiki. Of course you can enter your own categories on the fly and ignore the suggestions.

QUOTE (jdunham @ Feb 3 2009, 07:31 PM)

Just go into LabVIEW.ini and change all of your fonts to "Tahoma 13". It's just not worth the trouble to put up with the new font.

That's so great. Thanks Jason.

If anyone else is wondering how to do this just add the following to your ini file.:

BDFont="Tahoma" 13

appFont="Tahoma" 13

More details can be found in the http://wiki.lavag.org/LabVIEW_configuration_file/Fonts' rel='nofollow' target="_blank">LabVIEW Wiki here.

I installed Windows Vista on my PC. Now when I open old code which was written on Windows XP, all the fonts on the Vi diagrams seem to be slightly bigger. I notice this because text and string constants are now touching other objects when they weren't before. This also applies to bundle\unbundle nodes, properties etc. Anyone know how to fix this? I'm using LabVIEW 8.6. This even happens to newly created VI's

Is this just the new standard?

As mentioned previously, I've upgraded the LabVIEW Wiki to MediaWiki 1.13.3. I've also changed the look of the site to more of a traditional theme to make it look more like other MediaWiki sites, while still retaining the LAVA links along the top of the page. I think this will make it easier to read.

The big feature I've added is the new Rich Text editor. This is an extension which integrates the FCKeditor into the MediaWiki. More information about the project can be found here. I'll be making a video tutorial and a wiki page in the wiki help about how to use this new editor but until then, feel free to use it and play around. I'm hoping this new, easy to use, editor interface will be the catalyst for more article creation in the Wiki.

Even though the rich text editor can do a lot of things, it is not a total replacement for the text based editor. In some cases, you may need to revert to the standard editor to perform more involved tasks. You can quickly and easily switch between default and rich text editor whenever you need. It's also not recommended to use the rich text editor for editing wiki templates.

I think the new interface will be used for most editing tasks and will make adding content a lot easier for everyone.

Do you want to submit this to the code repository? You can get it on the VI Package Network.

OK, he's been deleted, gone, blown away and banned.

Ya, my point of posting this video is not to put down the city or for any negative response. I hang out in interesting video circles on the web due to my interest in video blogging, and this video popped up in our discussions. It's a great example of creating a desired mood and feeling. I know there are a lot of LAVA members from Michigan so I figured you might want to see it.

I've upgrade the LabVIEW Wiki to use the latest stable released version of MediaWiki.

One small problem after the upgrade: The editing toolbar has gone missing:

No worries, I know what the problem is but can't get to it until this weekend.

On the positive side. I'm also planning to add a WYSIWYG editor on the weekend too. Stay tuned.

For the record, I've seen that before too.

You know what might be better? What if we had a forum section specifically for *professors* to post their assignments, so that everyone in the community knows what the latest assignment is, so when a student asks a question, we all know it's part of his/her homework, and, further, there's a discussion thread that those students can all go off to to talk about possible solutions.

We should seriously make a page for this on the LabVIEW Wiki and link HH to it when necessary. can someone please do the needful?

So far I still haven't heard any valid arguments against releasing it in NI Labs. As the young people say: "All of them are made of FAIL and are pretty lame". Nice try though.

It's a fact that since the "secret" of scripting came out here on the forums, NI has been hiding more and more of the exposed features available with the hidden ini key with every new release of LabVIEW. There is still a lot of stuff under the hood that is not available by entering the hidden ini key. Also, what about xnodes? yet another piece of the puzzle that should be released at the same time as scripting. Hey, all the docs for Xnodes are on our Wiki.

Just hand over the docs for VI scripting to LAVA and tell us how to unlock it all and we'll take care of the rest. Seriously, no one will know.... :ninja:

Are you using the NI database toolkit? I know that it allows parameterized queries because I've used that in the past for blob data but was not aware of the 4-byte issue.

The only way I know to set the CLIENT_MULTI_RESULTS flag is via the ODBC driver. If you set the CLIENT_MULTI_STATEMENTS flag then this flag will be set too. Watch the video below to see how I enable the CLIENT_MULTI_STATEMENTS flag. I'm using ODBC driver version 5.1:

Here is some of the Twitter thread:

QUOTE

crelf Once again, LabVIEW scripting saves the day! I don't know how I'd program without it

jimkring @crelf We must legitimize scripting by creating great tools for solving important problems, thereby making LabVIEW a better platform.

NJKirchner @jimkring @crelf Sounds like synergy to me!!!

crelf @jimkring indeed.

crelf @NJKirchner Not that there's anything wrong with that!

MikeAivaliotis @crelf NI should just unlock scripting and give it to the community. NI Should embrace the community instead of fearing it.

crelf @MikeAivaliotis the documentation is much better in the latest versions, so maybe that's where NI's going?

NJKirchner @MikeAivaliotis Every AE on the 2nd floor just collectively cried out in pain and I heard it up on 8

jimkring @NJKirchner Why not release scripting in the NI Labs? Then NI wouldn't have to support it and AE's could sleep at night. Everybody wins.

crelf @jimkring @NJKirchner @MikeAivaliotis Awwww crap - what have I started?

NJKirchner @jimkring because the two don't synergize

crelf @NJKirchner Dodging the Question? You've been at NI for too long

jimkring @NJKirchner Sounds like you've got a new slogan and t-shirt: http://bit.ly/RoRm

njhollenback Show NI the money or a real strong value proposition

cloew @jimkring How is that differenty than what we have today? It seems people skilled enough to use LV scripting are already doing so

crelf @cloew @njhollenback @jimkring @NJKirchner@MikeAivaliotis All great comments - let's move the discussion over to LAVA.

jimkring @cloew I don't want to feel like an outlaw when I use LabVIEW scripting.

MikeAivaliotis @cloew It's easy for those on the inside. The old in keys don't work anymore. Open it up to all and we'll stop complaining.

jimkring "Legalize Scripting" would make for a great underground t-shirt for NIWeek 2009: http://bit.ly/YOEJ

I mentioned Releasing VI Scripting in NI Labs to NI right when NI Labs was first announced. Nothing has become of it however which is sad.

Question to you MikaelH: How do you get scripting enabled in 8.6?

Regardless of your fancy footwork, I would fail you because your app is dead in the water right from the start. I can't even run it because you've hardcoded a path to a VI:

If your app doesn't work out of the box, it's made of FAIL. It's like going to an audition on American Idol and you forget the lyrics to the song.

Some questions as a user:

• I see a Stop button. What are you stopping?
  
• Where's the Start button? What are you starting?
  
• Is the test information all controls or indicators? If they are indicators then how do you edit the info?
  
• What's Crossfire and Gamepad? Why are they important to me?
  
• Why does the indicator say Idle? Isn't it more important to know when it's running?
  
• Is battery level in Volts?
  
• I don't see any units in your Measurement table (or the graphs and legend)
  

All the above questions should be answerd easily by just looking at the UI. Anyway, I just did a quick pass at it. Also, I like to see the UI interaction flow go from Left to right (ie. Test Information on the left) but perhaps in China it's different.

I'm very excited to announce that LAVA has accepted an invitation to participate in the VI Package Network Beta. The VI Package Network is a distribution platform for tools created by the LabVIEW community. The LAVA Code Repository code will be made available for installation in VI Package Manager along side the OpenG add-ons for LabVIEW (which are already part of the VI Package Network).

Having the LAVA Code Repository code available on the VI Package Network will provide great benefits to the LAVA and LabVIEW communities such as:

• A wider reach for code developers to expose their work to thousands of VIPM users.
  
• Easier install and uninstall of LAVA CR code
  
• Easier upgrade to new versions of LAVA CR code
  
• Unique subpalette called LAVA with our logo.
  

LAVA CR Code will still be available for download from the LAVA website as before, however it will now also be available in the new VI Package (*.VIP) file format. LAVA CR code developers can opt out of the VI Package Network. In that case the files will remain in the ZIP file format.

Submissions to the VI Package Network should be in the VI Package format and can be created using VI Package Manager. JKI is generously donated VIPM Professional licenses to the LAVA Code Repository assessment team, in order to facilitate the submission process. More details on the new submission process will be outlined in the days to come and will be available here. Until we iron out the kinks, the old submission process using ZIP files is still in effect.

Existing LAVA CR code we will be gradually migrated to the new VI Package format and submitted to the VI Package Network. To facilitate this, I will be contacting every code submitter to get their approval and in turn coordinating the packaging and distribution process.

I'm very excited to see this development and look forward to having more high quality LabVIEW code available on the VI Package Network produced by the great talent here on LAVA. Please post any questions in this thread.

If you are a user of Twitter you will be happy to know LAVA now has a Twitter account here. We will be posting LAVA news on there and possibly links to noteworthy posts every now and then.

If you are a user of Twitter you will be happy to know LAVA now has a Twitter account here. We will be posting LAVA news on there and possibly links to noteworthy posts every now and then.

You guys are way too slow...

You guys are way too slow...