TobyD

QUOTE (BobHamburger @ Aug 5 2008, 08:52 PM) Thanks Bob! That should handle most peoples needs :thumbup:

QUOTE (BrokenArrow @ Aug 5 2008, 11:08 AM) The updater is at the end of this http://digital.ni.com/express.nsf/bycode/rdvbsi' target="_blank">knowledge base article. LV 8.6 will save back to 8.0

QUOTE (neB @ Aug 1 2008, 01:03 PM) The baby was yours!!!

QUOTE (normandinf @ Jul 29 2008, 10:03 AM) It's amazing how simple a solution can be once we understand the problem :thumbup:

QUOTE (Xrockyman @ Jul 29 2008, 07:48 AM) If you look at what you are sending to the XY graph you will see that all of the points are being plotted correctly. I do not understand why you think this is incorrect. http://lavag.org/old_files/monthly_07_2008/post-8758-1217346052.png' target="_blank">

Congratulations! Keep it up.

QUOTE (kmc @ Jul 17 2008, 07:14 AM) There's no need to answer a question that has already been answered. Normandif gave you the answer. You are using the correct property nodes, but you never set the bgcolor for the column headers (see table below from the help files). You can also use the paint tool to change the column header color if it does not need to change at runtime. Row Column Result –20Selects all cells of the first column, including the column header. –2–2Selects all rows and columns, including column headers. –10Selects the header of the first column. –1–2Selects the headers of all columns.

QUOTE (GaryTan @ Jul 11 2008, 02:41 AM) From the http://mindtrove.info/software/labview-webcam-library/' rel='nofollow' target="_blank">website's FAQ... QUOTE My webcam won't work with your library. All I get is a black image when I run your examples. Will it not work with my camera? Make sure you have passed the correct driver number to the Webcam Initialize VI. You can determine what the correct driver number should be by running the Get Digitizers VI included with the library. It will return a list of webcam digitizer names and their associated driver numbers. Pass the driver number shown in this VI to the intialize VI. Are you able to get each camera to work individually. If not, then get a second camera that is the same as the one that works. If you can get each to work individually, then you are probably running into an issue where the driver for one camera is not compatible with the second camera. You might be able to resolve the issue by creating a second copy of all the VIs in the webcam package and giving them each a unique name (I.E. Initialize2.vi, Capture2.vi, etc.). That way each can get initialized with its own driver and all communication with each camera will remain separate (I haven't looked at the code yet and depending on the architecture this may or may not work).

QUOTE (jlokanis @ Jul 11 2008, 01:20 PM) I did something similar a while ago but with a different approach. I simulated a "print screen". Yours seems a bit more robust and doesn't use unsupported functionality. :thumbup: The hide FP is also a nice touch. It's worth noting that the Code Capture Tool can do this as well. Here's the one I did. Download File:post-8758-1215814713.vi

QUOTE (JiMM @ Jul 11 2008, 09:01 AM) I couldn't agree more. I work with a lot of Vietnamese people who are always bringing me wonderful things to taste. Most of them are delicious, but I have not yet found the goodness inside a durian. Even when it's in my mouth all I can "taste" is the nasty smell.

QUOTE (BobHamburger @ Jul 10 2008, 08:37 PM) Nice tie-in back to the flower at the end :thumbup: . I agree that the project architecture is important, but that can also be made to stink by ugly code. You said you would "rather deal with a well structured application that happens to have crooked wires and overlapping block diagram objects, than a lovely piece of code that's written without attention to the disciplines mentioned (in your article)." I would agree with that only to a certain point. I think both style and architecture play a critical role in any LabVIEW application. If either one of them strays too far from the path of best practices, the code becomes unsupportable.

QUOTE (poiu77 @ Jul 10 2008, 11:50 PM) I ran into a similar problem a few months back. I ended up having to use a separate service to build my WSDL into a dll that I could then call from LabVIEW. We never could figure out why LabVIEW didn't like our WSDL (it worked in every other validator) but the dll solution worked for us so we didn't spend too much time on it.

QUOTE (GaryTan @ Jul 11 2008, 02:41 AM) Can you post your code so we can see what you have done so far. Also, what model of webcams are you using?

QUOTE (GaryTan @ Jul 11 2008, 02:23 AM) Welcome!

QUOTE (normandinf @ Jul 10 2008, 09:12 AM) I wonder if he an Mrs. Dopey have ever "hidden" in the elevator

QUOTE (Justin Goeres @ Jul 9 2008, 02:41 PM) SPOILER ALERT!!! Poor little guy never makes it. I generally prefer happy endings, but it did make me laugh.

QUOTE (Aitor Solar @ Jul 10 2008, 04:47 AM) There was also some discussion about this in an Eyes on VIs article found http://eyesonvis.blogspot.com/2007/08/for-loop-with-conditional-terminal.html' rel='nofollow' target="_blank">here. In the discussion, Robbie says QUOTE With a while loop, we don't know how big an array that auto-index terminal is going to create. So, we allocate memory over and over again (in chunks, but still possibly many times) until the while loop stops. With the For Loop, we at least know the maximum size that array will be, so we only have to do one large data allocation, and then resize downward if we terminated the loop early. To summarize, the For Loop w/Conditional Terminal is still going to be the most efficient loop.

Excellent video Tomi! And let me be the first to say thank you for not using youtube. The increased resolution of vimeo is nice. Did you set up a green screen to insert the expression flow background? Very cool! I have also enjoyed all the side discussion. I am consistently amazed at how much I learn by following these threads. :worship: -Toby

QUOTE (shoneill @ Jul 8 2008, 03:44 AM) I disagree with the idea that using the new feature is a "lazy way out which complicates things unnecessarily." I think Jim's article points out two use cases where the code is simplified, easier to read and more efficient. I personally find this new feature quite useful and I implement it often. I have found that it simplifies the code in cases where I need clean "last known state" error data when an error has occurred.

QUOTE (tcplomp @ Jun 26 2008, 11:59 AM) That's great! Thanks for sharing. It definitely brought back a lot of memories of some great times "playing legos" with my brother.

QUOTE (Xrockyman @ Jun 25 2008, 03:36 PM) Read up on Property Nodes. Specifically the Disabled property.

QUOTE (Justin Goeres @ Jun 24 2008, 07:25 AM) This is definitely on my list of feature requests. It's time to catch up with the rest of the world in the icon department. Well designed icons make code easier to read (although I would probably waste even more time designing my icons if I had the upgraded features).

QUOTE (Omar Mussa @ Jun 25 2008, 08:10 AM) Interesting. I have always found LabVIEW to be very stable (TestStand is a different story). There are times when I will leave LabVIEW open for days at a time and never have an issue. I will say though, that just recently as I have begun exploring the world of LVOOP I have experienced some random crashes and lockups. I can't say whether or not the crashes are directly related to LVOOP. It hasn't bothered me enough yet to search for a repeatable crash and report it.

QUOTE (TG @ Jun 23 2008, 09:59 AM) That was the exact same thought I had when I read that the images were deleted. Even the copy machines at work save an image of every document that is copied/scanned/emailed on an internal hard drive.

QUOTE (Michael_Aivaliotis @ Jun 18 2008, 01:34 AM) This is sweet! I'll definitely be watching for this one. :thumbup: