crelf

QUOTE (Eugen Graf @ Jun 10 2008, 06:17 PM) Do you want us to write the article for you? (really, I'm just kidding!)

QUOTE (neB @ Jun 9 2008, 05:57 PM) I remember a time a few years ago when I'd been working on a toolkit for about 10 hours, and then (through a drastic server failure or my own stupidity, I don't remember, must have been the former) I lost all the work of the day. I rode home, all cranky, and the thought of a much much simplier and intuative method. When I got home, I spent 45 minutes coding it up and was much happier. Maybe we all need a crash occasionally?

QUOTE (jdunham @ Jun 9 2008, 06:07 PM) Wow - that's one hell of a generalisation. Even the page that it links to is over simplified. Whilst I agree, at least in part, with the sentiment, I've gotta give my standard response to generalisations like this: "it depends" Saying "Don't optimize as you go" is like saying don't write using punctuation. Also "...making sure that the code is clean... and understandable" can be considered forms of optimisation.

QUOTE (neB @ Jun 9 2008, 05:57 PM) I can testify to that!

QUOTE (Eugen Graf @ Jun 9 2008, 05:21 PM) Oh - Okay - I didn't know that you were writing a tutorial. Good luck!

These are all great questions Eugen, but I'm interested in why you want to know - what are you up to? :ninja:

QUOTE (tcplomp @ Jun 9 2008, 04:51 PM) You're chances certainly aren't good This would be the perfect time to get your last version back out of SCC. You could try a LabVIEW brute force attack, but unless you have an idea of what the password is, it could to take a loooooooooong time (the password function in LabVIEW has a built-in 100ms(?) pause to make brute force cracking difficult).

QUOTE (James N @ Jun 9 2008, 04:06 PM) I was hoping that I could choose "none" for at least one of them...

QUOTE (tcplomp @ Jun 9 2008, 02:28 PM) That's the best way to do it - and then, if you like, you can use an OpenG function to rezie the FP to all contols/indicators at the end of execution. It's bad form to hide FP nodes unless you really need to - if you don't want the user to interact with them, it's often better to make them disabled and grayed.

QUOTE (rolfk @ Jun 9 2008, 01:04 PM) FYI: Here are the http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html' target="_blank">image guidelines. Please try to use only JPG, PNG and GIF file formats if possible.

QUOTE (Aristos Queue @ Jun 9 2008, 11:25 AM) Right - that was what I was thinking, but not typing I appreciate your elloquence.

QUOTE (Aristos Queue @ Jun 9 2008, 10:45 AM) So a wire isn't a node, but the act of branching can be considered a node?

QUOTE (shoneill @ Jun 9 2008, 09:19 AM) Good point.

QUOTE (Eugen Graf @ Jun 9 2008, 09:03 AM) Can't help you there - it's be far too long since I've used C. If you want to make a point, I'd prefer it if you could without referencing other languages - try describing it instead.

QUOTE (Eugen Graf @ Jun 9 2008, 08:45 AM) No, it doesn't. I see it as a pointer back to the output of the last node. That said, LVOOP wires might be considered differently, as branches instantiate?

QUOTE (neB @ Jun 6 2008, 03:33 PM) I always knew that Mars had a soft chewy centre...

QUOTE (Neville D @ Jun 6 2008, 05:05 AM) I understand. I'm not justifying anything, but my opinion on the history is: I beleive that NI didn't write the NI-Vision toolkit, so a license has to be paid to the author by them (and they pass the savings on to you!). The motivation behind the IMAQ hardware license might be based on hardware sales - if you buy one of their IMAQ cards (IMAQ, FireWire, &c) then you get a license for free, but if you're using someone else's hardware (including buses built into your motherboard) then you get hit with a license fee. That said, I'm totally ignorant on the real motivations behind licensing.

QUOTE (jgcode @ Jun 5 2008, 07:59 PM) I sure hope so! QUOTE (Aristos Queue @ Jun 5 2008, 10:21 PM) Yes, it would make a lot of sense to allow this for polymorphic VIs. Unfortunately, we didn't have the idea until late in the game and the architecture we use for testing scope has proven inflexible for making this work. It's a low priority desirable behavior. Thanks for the info Stephen - I figured as much.

Submissions are closed - now vote for your favorite design here!

The design submisison has closed - now it's time for you to cast your vote for your favorite front and back for the LAVA NI-Week 2008 T-Shirt! Rules: To vote, select a front and a back design for the t-shirt Select the item that corresponds to the name of the design file that you like Voting Closes at 10pm US EST on Friday the 13th of June, 2008 Please only vote if you're going to buy a shirt - don't force everyone else to wear something that you're not prepared to If you've got an entry you must be willing to provide a high resolution version if you win (if you can't, PM me and I'll remove it from the list) If you've got an entry you must own the copyright to it (if you don't, PM me and I'll remove it from the list) If you've got an entry that's not quite finished you need to be able to dedicate the time to finish it by 16th of June, 2008 (if you can't PM me and I'll remove it from the list) Entries: FRONT DESIGNS LAVAQR Spoolie BrokenArrow Supermen Avatars BACK DESIGNS NI-Week2008 99.7percent BrokenArrow NI-Week2008Super Volcano WireVolcano WireVolcanoSpagetti Superman

QUOTE (Justin Goeres @ Jun 5 2008, 08:59 PM) How about a combination? http://lavag.org/old_files/monthly_06_2008/post-181-1212717876.png' target="_blank">

QUOTE (MikaelH @ Jun 5 2008, 06:33 PM) QUOTE (Jim Kring @ Jun 5 2008, 07:07 PM) http://lavag.org/old_files/monthly_06_2008/post-17-1212707126.png' target="_blank"> You guys crack me up - that's awesome!

Wow - that's a mouthful! I'm just thinking out loud here: imagine I have a polymorphic VI (let's call it the "parent") which has some components (let's call them the "children") and I create a lvlib that contains both the parent and all it's children. Say I then set the children to private in the lvlib (you can probably see where I'm going here), but I leave the parent as public. Now I can't use the parent in a VI outside of the lvlib, because all it really is is a placeholder for one of it's children (which are private). Would it make sense to have private children of a public parent inheret the public attribute as a special case for polymorphic VIs only?

QUOTE (Aristos Queue @ Jun 5 2008, 05:02 PM) Well put Aristos (although I'm glad you didn't mention spelling ) QUOTE (Neville D @ Jun 5 2008, 11:29 AM) You need to load the latest version of the NI DAQmx drivers for those VI's to show up. ...or maybe you're looking for the older NI-DAQ VIs? Are you working on an old project, or are you starting a new one?