unicorn

Sorry about that. I tried it only with one page word documents. I expected the function Add OLE Object to be like Words menu Insert Object. So I would expect setting a little param would do. You could have look inside the NI Report Function. There you can learn who it works to handle Word documents. Microsoft itsself has got descriptions for all function, e. g. http://msdn.microsoft.com/de-de/library/microsoft.office.interop.word.shapes.addoleobject(office.11).aspx. Sorry but I haven't got time to fiddle about at the moment.

Take the NI_WORD.lvclass:Word Insert Object VI (Palette Report Generation > Word Specific > Word Advanced) to merge existing documents into a new one.

There are no "friends" in LVOOP. I think friend classes are workaround to reduce the need to access all class data via methods. In some case it makes programming easier. So in "classical" (non-OOP) programming everything was a friend from everything.

Do you really need that many indicators? Can they be grouped somehow so that you could show less indicators at the same time and than switch bewteen pages? What are they showing? Does the user/customer has to watch them all at the same time? He can't really observe 100 indicators. Perhaps it is sufficient only to pop up the indicators which show a critical state?

James! Drink less beer. What's about the attached VI (LV 8.6)? I tested it for two dimensions and one case only. horizontal concenate.vi

I get the solutions when I had stopped working on them. Suddenly there they are. I don't know who is putting up the big signs pointing to very stupid mistakes the next morning especially when I tried very hard on some challenges.

Maybe its due to a not up to date Adobe Flash Player. I opened the page with Firefox and it requested to install the Adobe Flash Player.

I think the figure ist just an illustration of the outcome of a specific test. So I guess it is not self-explaining. But if you imagine that only 50% of posible data paths in the code is tested and the code coverage will be multiplicative thru the hierarchy you will easily see that you need lots of test vectors to get a sufficient high code coverage for the overall code.

Now it has happened! The worst thing that can happen. I have spilled my coffee... over the keyboard... its a notebook... and over the mouse... Fortunately the right mouse button kept dry!!! ...but no coffee for the moment.

I am working with blue XP and see the strange behavior.

And with the first graphical UI you had pixels droping like snowflakes. I had it on an Commodore Amiga Computer but as a gag not as a virus. Nowadays with LabView Scripting SubVIs can drop to the bottom of the window, melt like icescream in the sun while the wires hang around like spilled spaghetti. And the best is the VI is still working... Or the VI on the BD become Helium filled while the wires hang around like garlands. Or some added inertia which let them follow a window movement with some delay...

I tried the Microsoftway (closing all windows and rebooting the system). Doesn't help. Is there any special content in the thread? I interrupted IE loading the page and I could read it partially. Micheal, is there something special about the image in your last post in this thread? Perhaps there is a plugin missing on my computer.

No, IE 7. A couple of hours ago everything was fine. But since the last two post were added I can't open it anymore.

I cannot open page 2 of the thread "Right-klick Framework". It always shows up an error saying that the web-site cannot be opened. What has happend? I received the following link for page 2: http://lavag.org/top...rk/page__st__20 Other LAVA pages work fine. Regards

River and Bottle would be Projects. You can do the described feature with projects (and manually resolving your name conflicts).

I have also test VIs (for testing special SubVI, classes or XControls) within a project, even within a class. So I have one, two many main programs. But most of them are used in the development environment. Usually there is only one VI which is build as an application. It a good point that VI modalize themselves when started and unmodalized when finished. Could be a radio button in the VI properties - customize appearance - dialog?

It is true what ESST says. If you need to reduce the risk then a big emergency button near the computer is the solution which should be implemented first. Regarding a floating window: make the window floating and not modal. (VI Properties > Category "Window Appearance > Customize... > check floating under Window Behavior)

I am interested.

What is about using VI server? The VI with the Stop button is running as a separate application and not as a dialog window. It opens a VI-reference to the VI to be controlled and if the stop button is hit the method "Abort VI" (using Invoke Node with the VI reference) is called.

If you would use the right click it would come out with a solution which unwraps the wires so that a crossing only looks like a crossing but is in fact just two touching wires as indicated.

That can become quite challenging if you think of making a pixel-type image with almost correct image colors by moving wires to front and to back. Not only the wireframe of Mona Lisa. But this can be done with a simple click if we would concentrate on the initial topic of this thread. Not only having coffee, meetings, argues with the customers ... Coffee is essential - must stop posting now to get some c

Is this the "management solution" to finish a VI?

Maybe it could also help to improve the clarity of the LabView menu a bit. But I am not sure. There a so many aspects involved. As a workaround until the code is ready would it be possible to plug one of your minions to a web server so that we all can paricipate?

I think people are taking advanced serious and read the manuals first before asking how to add two number in LV. The other side of the coin would be people asking for VIs doing the central thing of their thesis which they have to hand in this afternoon. And getting angry if there is no reply within 20 minutes.

Just another thought because I am working on an application where the data chunks have the same size as your: I am aquiring 600 images with SGL data type. I am writing each image immediatly after aquisition to a temporary directory and each image in a separate file which will be closed immediatly. I do it this way because the risk of loosing all images is reduced in case the application stucks somewhere. After finishing the aquisition process the separate files are copied to one file. If you are low in memory compared to the amount of data, you should avoid having all data in memory because Windows will punish you by intensive use of the swap file putting the throughput almost to zero. Regards