Mike Ashe

Need I say more? :worship: :beer: :beer: :beer: :beer: :beer: Great day Chris!

Done! One further comment, I gave high scores to both the small and poster sized versions of a new QRC. What I meant was that I'd like to see it split into two cards. A pocket ref and a poster for the wall above a desk. Last comment, it continually surprises me that in the job/dept/etc categories that there is no choices for consultants. I suppose System Intgration is applicable, but ... Anyway, good job on the doc's. NI doc's and support are well above the industry norm. Keep up the good work.

I cannot seem to find it right now, but this screen technology and another demo video from apple was posted here on LAVA somewhere. Would love to try it out. I'm sure we could figure out how to code LabVIEW with it. I had a short project that involved coding on an ELO-Touch touchscreen back in the mid 1990's. It worked, but it was a real pain, learning to wire with the tip of your little finger. :thumbdown:

I'll agree heartily on the first, but as to the second, well, some of us occasionally might have used one, but we don't admit it in polite company Seriously, I'd really like to see wire labels. I think it would add a lot to comprehension of diagrams. I would also really like to see some indication on a BD object that it has description data. A little star or triangle in the corner or something.

Hello Aggie! Welcome to LAVA. What type of applications do you use LabVIEW for? Good idea to "dig", ie, use the search functions in LAVA. Many questions get asked by new members that were already discussed somewhere in the LAVA forums. Good luck.

Didn't check the exact item above, but the shorter: transparentBDLabels=True works on my 8.0 install, in fact, when I checked for the free labels version I saw that I already had the shorter version in and I can't remember when I put it there.

Hello Nanbe1st, welcome aboard. Could you tell us a little bit about yourself and what you are using LabVIEW for? What are your interests?

Welcome aboard Rock! When you say bridge testing, I assume you mean traffic bridges? Lots of vibration and strain gage testing?

These are awesome! :beer: :beer: :beer: Got me thinking for some other signs, like Homework Hustler Alert! "HH Alert!"

Idea for future challenge: I'd like to see something involving the picture control, which I think is under utilized. Perhaps some subVI - algorithm that recognizes when you have "selected" various shaped objects or drawing artifacts in the picture. Or a really efficient way to create a highlight on the picture around an arbitrary object, either a glow or walking ants. Another topic I'd like to see is a challenge that uses one of the GOOP implementations in a specific way. Not a whole application, just the best object class and concise method set to implement an item. (maybe a picture control drawing object?).

You might try posting on info-labview. Many thousands of people read it every day (or every other day...). Another thought is that if you really want to get better, a lot better, 1. Have you gone through every (and I mean EVERY) example in the /examples folder that ships with LabVIEW. Studied them? 2. What are the LabVIEW books that you own and have studied in detail? If the answer is "not many" then go to Amazon.com and search on LabVIEW.

Nice update! Thanks for continuing to contribute and support the code you have contributed!

Specifically, you want this topic: Case Structure - Is it possible ... The second post should have the "Select-A-Case" zip file which will do and show all sorts of things with cases. Nice toy to have around, even if you don't need all of it right now.

Hmm, without spilling too many beans, let me say that I am actually tryng to do the same thing in more than one OO implementation. I am using the Open Source GOOP Template, the dqGOOP and possibly one onther. My reason is to find the optimum implementation for long term development of the project. I also am experiementing with a sort of pie-in-the-sky ideal of being able to use different implementations of GOOP in the same framework and have them act as interchangable plugin layers. It turns out that the different GOOP implementations are not all equal (obviously) and their are rather large speed and efficiency differences. As I said above, I am still making the transition myself, and there are several others here on LAVA that have a lot more experience with GOOP's than I do. I am not currently using the new NI built in gOOP at all, and probably will not for the forseeable future. First of all, I'd like to have backward compatibility as far as possible. Secondly it is new, and as much as I love LabVIEW and the NI team I have to say that most of the nifty new features or products are NRFPT in the first couple of versions. Perhaps I'll look at the new NI stuff in LabVIEW 9.x or 10 ... As to how, what, I am looking at objects being open files, internal data structures, GUIs, ... don't really want to get into more project specifics just now, sorry.

The FOSS article was interesting to read (again) and see the various takes posters have expressed in this thread. Right now I am doing some ATE work for a large defense contractor. Funny, but I don't think FOOS will catch on here any time soon. The reason is the legal department. They don't want engineers to use FOSS or OpenG or anything not "shrink-wrapped" with a commercial license, due to possible exposure to litigation. The reasoning goes that if they start using a lot of open source stuff they might be sued by someone (party B) who claims that that B's code was wrongly included in the open source code and ... yadda, yadda ... Since a lot of big litigation goes after whoever has the deepest pockets, regardless of actual fault, the big companies can be gun shy about using FOSS. I haven't given up on trying to convince my current client to open up to open source, but it is proving to be an extreemly uphill battle. Again, a reread ... what I found most applicable this time was this line near the end: "And in the commercial corner is software that can never be FOSS. It might be encumbered by patents, or more likely, is sold as an adjunct to some piece of hardware, such as "embedded" software found in modern cars, printers, scanners, wrist watches, cell phones, and so forth." Hmm, sounds amazingly like LabVIEW; protected by patents, attached to HW, etc, etc. Except that now that the patents are running out there is a chance to start into stages 5 & 6 of the FOSS cycle.

Hmmm, You have several different options. 1. Use a Waveform Graph and implment the history feature of charts using a circular buffer VI in your diagram. That gives you the cursor functions, but you have to do extra managment behind the scenes. 2. Use an Event structure to get Mouse Up/Down/Move on your chart and from that you can get mouse coords, but then you have to do your own conversion to Y scale points, etc. 3. Plot your data to a picture control (see the example VIs with LabVIEW) 4. Perhaps find an XControl that gives you this combination of functionality, but I have not heard of anyone doing this yet. (That doesn't mean it hasn't been done, go look :-)) Good Luck

As someone else pointed out, not much. Might I humbly put in a plug for reconsidering option 1? In my estimation, the picture control is one of the most powerful, yet under utilized features available in LabVIEW. Yes, it will take a little work to get going, but a few *well thought out* VIs for implementing your current requirements using the PC could be very handy later down the road. YMMV, good luck

Open the file using the Advanced File Functions >> Open File with Deny Mode set to 2, then use the Read File and Write File nodes, setting the file pointer (or "mark") as needed. Under the palette: File I/O >> Advanced File Functions >> Seek The Seek primitive will set the file pointer (mark) to any location in the file you choose, for use by the other nodes. You will have to keep track of the file "housekeeping" yourself. If you want columns you can create them yourself, but it would probably be easier to use the spreadsheet functions.

I hope you find a license model you are satisfied with. As a last resort, however, you could always write your own and submit it to The Open Source Initiative as they serve as a source for many "approved" open source licenses. Remember also that you do not have to have someone else's approval. You are free to license any way you want. I would suspect taht one of the OSI versions are suitable or close enough. Good luck.

Congrats on your third! (We stopped at 2). And no problem on the liquids, duty-drivers are always welcome (and sometimes they come back from the parties with the most amazing blackmail photos...)

Agreed, just as LabVIEW and dataflow are a way of thinking. It is pretty easy to see where someone has thought in "C" in their head and then translated into LabVIEW. I suppose the same is true for OO-LV vs non-OO LabVIEW style. I'm still making the conversion myself, having been rather set in my ways after 15 years with the language. (I have a long delayed pet project that is being rebuilt in OO now, it's just a lot of work). That all being said, I think it is important to retain the ability to NOT program in OO once that is your dominant style. Using OO-LV or C++ to write "Hello World" projects is overkill. On large projects, with significant lifecycles it is invaluable.

Very nice, I've wanted something like this for a long time. One thought, in many auto complete implementations I've seen the text is accepted when you either click outside of the control or if you hit <ENTER> while the suggestion is in progress. I te4sted your control with Tools >> Options >> Front Panel >> End Text with Enter turned on and it worked fine. Might want to give a note in your top level test VI that this is an option. Thanks again, this is great! I'm now thinking of some modifications to check for certain formats in the entered string, like auto phone numbering or auto date or SSN, etc.

Good grief, at those prices maybe I should take a sabbatical from LabVIEW and make Visio stencils for a few months

Anyone who has a legal hard copy can sell it legally. I note that the person requesting the course has LabVIEW 7.0 listed as his version. You cannot get NI to sell you an older version of LabVIEW. I am not sure if they will sell you an older version of the Intermediate course. It might be worth calling and asking. If they say no, then you can go on searching for a used copy. Depending on your relationship with your local NI rep and the closet Certified Training Center you might find an older copy available there. I agree with CRelf that however you get it, it should be a legal way. A flipped softcopy is not the way to go, bad habit to get into. That being said, if you want a good basic to intermediate book, might I suggest the new version of: LabVIEW For Everyone, 3rd Edition At $70.00 it is a bargain.

I also have been getting the digest version of IFLV for a long time and therefore am always one clock cycle behind. I found it invaluable when I was first starting out in LabVIEW and I tried to contribute a lot in the late 1990's. I find that most of my time for such things is now spent on LAVA, but I would still hate to see IFLV go away anytime soon. The text only format can be nice at times and is readable on a PDA or cell phone. Trying to run a browser on a PDA gives me eyestrain. If IFLV ever does go away I hope that all the years of posts can be archived somewhere, preferably here at LAVA so that they are not lost to posterity. It would be a shame if all that help and history was lost.