Yair

A type cast takes the bit pattern of whatever you wire into it and reinterpets it as the new data type. The actual data (as you saw in your example) does not change. In this case, the type cast is only necessary because the editor does not let you see the Text property when you use the StringConstant class. If you had wired the numeric class to the top terminal, you would have gotten the numeric class properties.

I understand that the "whopping" part is not your opinion, but why bother? Worst case scenario, you have to email the executable and instruct the client to download the RTE from the web (if you have somewhere without a web connection, you might as well send them a CD). NI presumably puts a lot of design and testing into the development of the RTE and installers for each version and attempting to work around that with each new version sounds like a lot of work for little gain (unless you wanted to be able to run something without installing, which is not your case). I doubt you will find many people who can give you a definitive answer, as this is clearly unusual usage.

Stephen, if I remember correctly, the documentation for the Get Diagram Image Scaled method used to say that it would work in the RTE (when used on a VI with a BD, obviously), but the method itself did not work. Is this still the case with 8.2?

Crosspost. When cross posting, it is considered polite to provide a link to the other thread to avoid having people waste their time if answers were already given.

I'll be sure to shout you my congratulations when you whoosh past me. (Is he really only 60 posts behind me??? I guess knowing a thing or two about the computer science side of OO helps...) BTW, why jimi?

Another Cross-post. If you are cross-posting, it is considered polite to include a link to the other forum to avoid having people waste their time if an answer was already given.

Crosspost.

Brian Tyler is the head of the LV team responsible for these things and likes these questions. You could try dropping him an email through his blog (called Lycangeek) or post in the NI LabVIEW board, where he's likely to see it.

As far as I can figure out, the license agreement (at least for 7.1) says that you have to put the text in the application's about box. Some of our applications are distributed without about boxes (they run full screen with no menus) and so they do not have this text. I don't know if this is problematic, but that's how I read it. In any case, the client doesn't care what the system was written it, as long as they get results.

To rotate a dial you need to place the cursor over the end of the scale and you should get a rotate icon. Clicking and dragging at this point will control this. You should note that doing this at the low end of the scale will cause the scale to be rotated as-is and doing this at the top end of the scale will allow you to control the size of the gap between the end and beginning of the scale. In Norm's example, the scale end (and beginning) are found at the bottom of the dial, where the green and red meet. I wouldn't be surprised if you could get cooler effects from a picture control, but they would require more work.

Well, at least now I know that Marmite has some real use.

I was browsing SourceForge and I happened to run into this current project. Does anyone know any of the guys on that project? I didn't recognize any of the names, and was wondering whether some people here would like to help them.

If the Application class does have this method and it's simply not exposed, I'm wondering whether type casting it to the generic class would do the trick? Of course, you would need to find the property indexes to test this, and attempting to automate this crashes my copy of LV, but I'm fairly sure I saw a list of indexes around here somewhere (maybe Brian posted it?).

Interesting. I remember checking out those VIs some time ago, and I don't remember finding a wait which was too long. Apparently, I wasn't looking hard enough.

Nice... :thumbup: I especially like the icon.

Helo. my techer give us asinment to calc in laviuw and i need help :worship: :!: :ninja: can you help me pleeeease??!!!! the asinment is Calculate using LabVIEW how much wood would a woodchuck chuck if a woodchuck could chuck wood. can you pleease help me!!! i need it tomorow!!!!1 thank u

Unfortuantely Darren decided to stop with the nuggets, but Ben suggested that the community tried to pick it up, so maybe some other contributor will use this.

And so are the storage VIs.

I can't see your VI, and I wouldn't be surprised if you took the same path, but how about this simplistic approach? Add some bells and whistles and it would be very nice. Download File:post-1431-1169317864.vi

Welcome to the community. Be careful, once you will get used to LabVIEW, you might not want to go back.

What, you mean the 8.2 version of what's pointed to in the first reply?

You could potentially use the Windows function CopyImage, but that looks like a bad solution to me. I think I would also go with something along the lines of Ton's suggestion of calculating the position based on the column widths.

Add this code to your VI: