Yair

I managed to download 130 MB of the file using IE (which varied between 8-80 KB\s) before I experienced a local power outage, which caused my internet connection to die. I also think I remember downloading other files which were several hundered MBs using IE (I don't remember which files, though), so either I'm the one in ten, or IE works OK now. After the power was back I restarted with DAP and got it all at around 200 KB\s (DAP simulates several users downloading at the same time, allowing you to get better speed).

Mike, if you liked the movie, you absolutely have to read the book. It has a whole darker and much funnier aspect which has been completely cut out in the movie adaptation (which shouldn't have been too hard, as you will understand when you read the book). William Goldman, who wrote this, as well as "Butch Kassidy and the Sundance Kid", definitely has a sense of humor. One word of warning, though - do not let your children read this book. If you do, that's at your own risk. Incidentally, if memory serves, the name is actually Dread Pirate Roberts, but it doesn't look like the invision board gives you the option to change your user name. And if you people like pirates, you should play the Monkey Island games. As for LLBs, one thing I do use them for is polymorphic utility VIs. Since I have backup for those VIs, I don't really mind corruption, and they're easier to organize.

If you want to set a control, you can try using the VI class "Set Control Value (Variant)" method. This will allow you to use a variant directly, but has its own dangers and downsides. If you want to convert the data into a wire, you will have to have duplicate code at least to some degree, because the wire coming out of the function can only have one data type. You can have this duplicated code in polymorphic VIs, but that will also require some work. The OpenG VIs use the Type Descriptor to process the data. You could do the same, but since the work was already done, it seems a shame to do it all over.

And let me guess, you liked it mainly because of Burtie boy's "surprisingly good performance" and not at all because of, oh, let's say, things like the topic or like Heather Graham's "scenes", right? Did your wife like it as much?

At least that part can be handled by letting LV find the BPs for you using the Edit>Find option.

I hope you see the funny part now. These things usually rely on context and everybody know that you can't explain a joke. As a side issue, maybe we should start a poll: who do you prefer - Jodie Foster or Burt Reynolds. Dr. Jodie Foster - Multiple Oscar nominee and winner. Participated in things like Contact, Maverick, Taxi Driver, The Silence of the Lambs and The X-Files. Or Burt Reynolds - The man and the moustache. The star of classy films like The Dukes of Hazzard, Driven, Universal Soldier 3 and Cop and a Half, alongside some better stuff like The Cannonball Run and (again) The X-Files. You know what my pick is.

To clear a brekpoint on the outer frame, you usually need to click on the border of the structure itself. If this doesn't help, for some reason, you can right click and remove the sequence and then rebuild it.

Funny is a relative term. As for the joke, try looking up the relation between Jodie Foster and John Hinckley's attempt on president Reagan's life.

You can customize a boolean control to have an image by right clicking it and selecting Advanced>Customize. You should read the LV help and user manual about how to customize controls. Another option is to use a combination of a picture control and mouse down events, so you can even change your pictures. A third option is using a picture ring, which allows you to hold several images. You can disable the control and detect the mouse down event for it to know when it was clicked.

Well, if the fight between Blue-Ray and HD-DVD is down to Jodie Foster vs. Burt Reynolds, Then Sony definitely have my vote. :thumbup: After all, she did do Contact, one of the movies I liked most in the second half of the 90s (particularly the effects). ___________________________________________________________________________ Hmm... for some reason I feel like going out and shooting the american president. :ninja: Will this get the FBI on my back? I guess it's time to and go into hiding.

I have no experience with using LV in medical fields or with directly comparing LV to other languages, but I will give you a general answer. First, to get real time performance, you will need a real time device with a real time OS. You will also need RT programmers. These should all affect the decision. For example, is there Java support for real time platforms? Do you have access to LV programmers with experience in RT programming? There is no direct relation which says "LV will take twice as long to execute a loop", but in general, it is considered to be slower than C, even by NI. However, NIs RT devices can be very fast, and have been used in the medical field (search NIs site for examples). These targets also have built in ethernet handling, which is good for wireless comm. The bottlenecks are often in the I/O itself, in things like handing really big data structures and in non-deterministic operations, like file I/O or communications. Managing memory in LV RT is very important - you need to make sure you don't continuosly allocate more memory and that your deterministic operations are shielded. The best solution is probably to get a LVRT programmer or to take one of NIs courses (and at least to read about it on the net).

What you want is a .ctl file which is set up to be a typedef. A typedef, unlike a standard control, will also hold on to the values you give it, so when you update the typedef, the values will be updated whereever it's called. Just search the help or the user manual for "typedef".

Well, "that country", at least to an extent, is part of the US, so I think you should be covered. Besides, many countries (with useful extensions like .tv or .to) allow outside companies to buy their domain names. I think you can even get a European Union (.eu) domain without being a European citizen.

A short list of interesting features which are hiding in the upgrade notes can be found here. Some of these are very important.

A. Because it allows you to manipulate each control individually. B. Because to import those settings into an EXE you need to redefine them or put them into the INI file, which is annoying. But mostly because of A. I agree, this would definitely be a nice feature. In fact, I think that almost anything that can be set through menus should also be set through property nodes.

How about the property Scale.Flipped (and no, there doesn't seem to be any good reason why it wouldn't be called "Inverted" as well)?

If you really want an answer, you should probably lead by example. Why not describe your own experience in more details? :question:

I have had cases where I did testing on VIs which weren't running. Warren, there is one way you can get rid of your Aargh!!! - use the VI class properties FP.CustomTitle, FP.Title, Name and the ones in the modifications section to determine what the title will be. That way you don't have to try and then check for errors.

Do a google search for them. If I remember correctly, LabVNC was written by Jeffrey Travis and his email should probably be available on his site.

OK, some additional checking has shown that the duplicate taskbar buttons appear because of the windows shape. Adding a delay before making the window round (I gave it 5 seconds, but 1 should probably be enough) will cause the second button to disappear. Then, using the VI I attached above, we can get rid of the VI window button and you have a clock with no buttons in the taskbar. Now, the only thing remaining is to control it through a tray icon using only DLL calls (no ActiveX), which I have no idea how to do.

The transparency is achieved by a single VI calling a single windows API function, which is simply based on code I found elsewhere here. Try searching here for transparent to see what you can find (although the code there probably isn't 6.1). This is what the code looks like. You can find the function descriptions in the MSDN and the VI seen there is from winutil32 which can be found on NIs site. I'm not near a computer with 7.0 at the moment, and part of the VI won't work in 6.1 anyway (the mouse input VIs which are used in moving the window), but I can backsave it when I get to one (not soon), although it will be broken. The other interesting part is the VIs for making the windows round which can be found in one of LTRs past challenges.

As I mentioned one post earlier, I already tried that. I know that trick (used it quite a few times) and I did have Clock.exe, Clock.ini and inside the ini file a section names [Clock], but it didn't work. Like I said there, my guess was that this was because my top level VI was missing something (the title bar?), but maybe I made a mistake. Did you try building it into an exe and using that line (without the addition of the latest VI)?

And one more addition - a VI that hides the taskbar button. Like I said in my last post, for some reason the LV window did not disappear in the EXE, so using this only causes one of the buttons to disappear, but if you do this inside LV, the button will disappear. You can call this VI when the clock VI stops running and it when it stops, the window will return to normal. Minimizing the window in this situation causes it to become a "floating window" which can be restored. Download File:post-1431-1126443834.vi

No, just tried it. The winutil VI posts a minimize message to the window, which, I assume, is the same thing the property node does. It seems there is some difference between the minimize button which is part of the window and an external minimize message, although I have no idea if that difference is at the windows level or the LV level.

There actually does seem to be a problem - it seems there is a bug (at least in 7.0) where minimizing a window programmatically causes mouse enter and leave events to stop responding until you enter another LV window. This means that if you make it into an EXE, you can't minimize and preserve the transparency (which now relies on the enter and leave events). I posted an example here. Another thing I noticed is that I couldn't get rid of the second task bar window in the EXE, even when using hiderootwindow=true. I'm assuming that an application where the top level VI does not have xxx (probably the title bar) must have the extra window to keep the RTE open.