Yair

I don't know if this would constitute a bug or not, but the description of the problem would be that the Get Panel Image method captures only the FP itself and not the background image. The method itself is older than the background image feature, so it's possible that when that feature was added, no one thought to update the method as well. Personally, I would call this a bug, and it's worth reporting to NI. As a side issue, we have a tool for capturing code images which might make your life easier. It uses the same method, so it won't solve this specific problem, but it might help for other stuff.

QUOTE (Norm Kirchner @ Aug 18 2008, 06:53 PM) Why would he do that when he already has the G-Man from Half-life, who's far more creepy?

I remember using a 4D one once (it had a changing parameter and each time it was changed it had several runs with each run recording more than one value). My boss also did a 5D once, but I don't remember the details.

QUOTE (jgcode @ Aug 17 2008, 06:20 AM) I would call that reasonable or stupid, not merciless. All things being more or less* equal, a spelling mistake on the document which is supposed to present you to potential employers is a reasonably valid reason to get rid of someone without giving them much thought. The stupid option is if you have someone who's highly qualified and you throw out their resume based on an itsy-bitsy speelling mistake. I don't really do sales much, and around here it probably wouldn't really matter anyway, but I suppose certification could matter to companies seeking work - if you say "I have 3 CLAs and 20 CLDs" you might get a better chance if they don't know you. * More or less - with an average tolerance of no more than 4.7%. See IEEE 4342.F.

This is what I meant (7.0). I couldn't find the post after a quick search, but I had it on my hard drive.

QUOTE (jgcode @ Aug 15 2008, 05:54 PM) Actually, it wasn't. I was refering to a right click context menu, which would be more relevant in your case. P.S. If you come up with something, why not post it?

If you search PJM's posts, you should be able to find a pure G implementation for a nested context menu. You can adapt this using a picture control to do what you want, but it will probably require some work. Have fun. :headbang:

QUOTE (jdunham @ Aug 14 2008, 09:07 PM) No. Our usual workflow has a single developer working on any module at any one point in time and we have users with different levels of experience with both LabVIEW and SVN. As a result I prefer having the developers save and commit all the VIs when changing a typedef so that we know that we have a single version and that when you open it nothing should recompile. Also, our software is often deployed on a single computer, so we don't really have versioning issues. For the same reason (and simplicity) I also prefer commiting executables. Just the other day a client wanted me to revert an application to an older version to demonstrate that there wasn't a problem with the recent code changes. Instead of having to dig up a CD or check out all the relevant code, I just reverted the executable to the relevant version, something that took about 10 seconds. That's where SVN's efficient binary diff which was mentioned earlier comes into play. The reason I do this is that hard drive space and network bandwidth are cheaper than headaches. That said, this works for our specific situation. It's definitely not for everyone and it might not even work for us in the future. By the way, for those still not convinced about using SCC, here are two good reasons: 1. Easy backup. 2. Easy synchronization. If you have more than one developer, you must have some sort of synchronization. At least in TortoiseSVN, this is very easy - two mouse clicks in Windows Explorer and your entire hierarchy is synchronized.

QUOTE (jdunham @ Aug 14 2008, 07:45 AM) Have you tried Options>>Environment>>Do not save automatic changes?

QUOTE (normandinf @ Aug 14 2008, 03:25 PM) I don't know about there, but over here you'll find a story during every election about how some dead people were able to vote.

I worked on an application which involved measuring temperatures (among other things). During the development and testing phase, the programmer who worked on the connection with the instruments (who used to wear a leather jacket all the time) hooked up a few sensors to test the system. Showing the resulting graph (around 20C\68F) to his boss didn't help and now he works elsewhere. :laugh:

QUOTE (crelf @ Aug 13 2008, 11:06 PM) Weeeeelllll... Actually, there are a few ranging between reasonable and good, assuming you like pop music. Incidentally, since I mentioned "the black rider", I really should get around to opening an audio editing program and tacking a "Wiiiiiilma!" onto the end of it.

I like mixing anything from cheesy pop to obscure bands. Here is another selection (I wrote a quick VI to extract a random list): ABBA, Al Stewart, ELO, Jethro Tull, Ayreon, Bee Gees, Beach Boys, Bill, Black, Bonnie Tyler (yes, I said Bonnie Tyler. What of it?), Boston, the Cardigans, Chris Rea, Bowie, Dido, Echolyn, the Eurythmics, Harry Chapin, Iron Maiden, Johnny Cash, King Crimson, No Doubt, Paula Cole, Patti Smith, Roxette, Roxy Music, Rush, Sarah Mclachlan, Scissor Sisters, the Scorpions, Squid, Sting, Suede, Suzanne Vega, Ten Jinn, Ultravox, Yngwie Malmsteen, No Doubt, Kashmir, Gentle Giant, Porcupine Tree, Mike Oldfield, Mark Lanegan, the Dukes of Ted (Altenbach's son is their sax player). By the way, in keeping with the original post, I do actually occasionally select some songs which divert people's attention on purpose. Examples that come to mind include Snow's "informer", M.C. Hammer's "can't touch this", "macarena", bad Eurovision songs and Tom Waits' "the black rider". Usually they can't work then. :laugh:

Good thing she never watched the care bears.

Which property of the menu ring are you refering to? Is it the way it looks or the fact that you can change it dynamically? Obviously, you can't change strings in enums dynamically because they're part of the data type. If you want a similar control which outputs strings you can use the combo box (from the string palette). If you want an enum which looks like a ring you can use the system enum. If you want LabVIEW style controls, I think you will have to do some customizing and copying of images to get the look you desire.

Hugely impressive.

QUOTE When you click on which block diagram? Did you try opening the LLB using File>>Open? Did you try placing it in user.lib and then looking in the palettes?

Did you change something? It certainly didn't work when I posted that, but those two do work now. "kermit mel" returns this thread. Is it possible that the Google algorithm is affected by our activity?

I usually randomly select songs from the music I have on my hard drive. The others usually like them and I usually mix them unless they go together. Here are some example of songs we heard in the last couple of days. I selected these specifically because they're related to what people already posted: Queen (don't remember which song off hand). Tie a yellow ribbon (YEAH!). Dream Theater - Wait for sleep. All of the four seasons. Pachelbel's Canon in D. Dire Straits (not from Brothers, but Lions and Down to the waterline). Simon and Garfunkel - The sound of silence. That of course was just a small selection, since during the course of the day you can here dozens of songs.

And now we know why Chris has so many posts. :laugh:

By the way, this still seems to suck. Examples: "kermit mel" still does not find the thread we discussed earlier. "search sucks" still does not find this thread. "labview tool suggestion" (what I was actually looking for) does not find this thread. All of them seem to work fine through labviewsearch.com. Maybe the internal search engine just isn't indexing the content?

QUOTE (Jon Sjöstedt @ Aug 11 2008, 12:01 PM) http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=305242#M305242' target="_blank">This example is implemented using dqGOOP. You also have VIs there which you can download to see how it works. P.S. Christian, nice work on the CVT and the components in general. I think creating tools like this is very useful. Any reason why these components don't ship as standard in vi.lib?

So NI released their version of this tool in LabVIEW 8.6, and now that it's out, I would advise people to try playing with my tool a bit. The reason is that it has a couple of features which are implemented differently than in QD (better, IMO) and if other people think so as well (and tell NI about it), then NI will hopefully spend the time implementing something similar. Specifically, The selection is done differently. QD uses a combobox with autocomplete and only moves to the listbox if you use the arrow keys. DI uses a string control and always has an element selected in the listbox. This changes where your focus is. Both methods have merit, but I believe mine has advantages because of the following point. When you have more that one match, and you do want to use the listbox, you have to shift your attention there. If many of the things you drop are like that, you might find that you always look at the listbox instead of the combobox and thus miss the autocomplete. Since I have used my version a lot and I haven't used QD much, I can't say for sure. My version uses a more intelligent sort algorithm, making the result feel (IMO) much more natural. Again, this matters less if you're using shortcuts all the time, but I have a feeling many people won't use them much of the time. Two specific differences in this algorithm are that DI uses a preference algorithm, so that when you use a specific name more often, it's more likely to be selected and that it gives preference to a match which is in the beginning of a word and\or close to the beginning of the name.

QUOTE (Phillip Brooks @ Aug 8 2008, 08:02 PM) http://forums.lavag.org/-t8976.html&view=findpost&p=35228' target="_blank">Here? As I mentioned (and demonstrated) there, and as mentioned here, you can use shortcuts (or aliases, as I called them) to do this. "mod" was one of the examples I used as well. Another was OpenG's "Conditinal Auto-indexing Tunnel", which I could never remember, so I simply gave it the alias "filter elements from array". By the way, now that QD was released, I would advise people to try playing with my tool a bit. The reason is that it has a couple of features which are implemented differently than in QD (better, IMO) and if other people think so as well (and tell NI about it), then NI will hopefully spend the time implementing something similar. Specifically, The selection is done differently. QD uses a combobox with autocomplete and only moves to the listbox if you use the arrow keys. DI uses a string control and always has an element selected in the listbox. This changes where your focus is. Both methods have merit, but I believe mine has advantages because of the following point. When you have more that one match, and you do want to use the listbox, you have to shift your attention there. If many of the things you drop are like that, you might find that you always look at the listbox instead of the combobox and thus miss the autocomplete. Since I have used my version a lot and I haven't used QD much, I can't say for sure. My version uses a more intelligent sort algorithm, making the result feel (IMO) much more natural. Again, this matters less if you're using shortcuts all the time, but I have a feeling many people won't use them much of the time. Two specific differences in this algorithm are that DI uses a preference algorithm, so that when you use a specific name more often, it's more likely to be selected and that it gives preference to a match which is in the beginning of a word and\or close to the beginning of the name.

QUOTE (Jon Sjöstedt @ Aug 8 2008, 04:30 PM) There are never any guarantees in software, but you should try to diagnose the situation to see what went wrong and what can be done about it (e.g. maybe OOP wasn't appropriate, maybe it was implemented by people who didn't understand the concepts, maybe it wasn't designed well enough) QUOTE I'm also impressed by those *OOP-packages that allowes access to data using ref's and would like to know if there is an easily reuseable method behind it. These tools usually have a template and a wizard which copies that template, so that much is reusable, but you usually don't need to know about it, because the wizard does all the work. If you're asking about whether you can have inheritance or write code for one class and reuse it, that highly depends on which implementation you use and how you write your code. Some of these are free (like dqGOOP), so you can just download it and see. QUOTE By experience I guess that the newly introduced (lv8.2) OOP-constructs are not that reliable (I am unfortenately stuck with lv8.2) until a few versions later. I don't know any specific details, but there were certainly issues with LVOOP in 8.2 which were resolved in later versions. You can see details by looking through this board and looking at NI's known issues documents.