Application builder and CWGraph3D

[Radman]

Hello all,

I am trying to build a self-executable 3D plotter for a fellow worker using the CWgraph3d. When I go to build the application with application builder I have no issues. When I install the application of the host computer and try to change the 3D plot properties, I am not given the options as when I ran the program inside of LV....Any ideas on what I am doing wrong?

Thanks,

Jay Poret
AOT, Inc.
jporet@pica.army.mil

[Robert M]

The 3D graph CWgraph3d is actually an ActiveX control originally written for ComponentWorks (hence the CW), which was the forerunner to MeasurementStudio. If you want the full functionality for the 3D graph, you will have to add the .ocx file as a support file and run a batch file to register it on the host machine. There is a Knowledge Base entitled LabVIEW: Advanced Application Builder that does exaclty this as one of its exercises. Follow the directions there, and you should be good to go. Let me know if you have any trouble or futher questions, and I'll be happy to help.

Have a great day!

[Radman]

Thanks for the reply.....As I tried to work throught this exercise, I have some maybe stupid questions....what is the purpose of including the datasocket as top-level VIs? I tried to build the application without them but it dosen't work....Another thing I became concerned about was the batch file....From what I gather it tried to identify the OS and then decides where to insert the .ocx file....What I will need is a Win2000 entry and Win XP entry....do you know how to modify them to look for win 2000 and win XP?

Thanks for oyur help....

Regards,

Radman

[THailey3]

Hi Radman!


Maybe Robert will have more to add, but I'll throw in my 2 cents worth 🙂

When creating an executable/installer, setting Top-level VIs is what designates what VIs actually open and run when you double-click your exe file. By adding both the DS 3D Graph Reader & Writer as Top-Level VIs, you are indicating that when running the executable you want both of those VIs to automatically open and run.

Now about your concern for the batch file. This document was originally created before the release of Windows XP. With that being said the following:

"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on NT, ME, and 2000, and the System directory on 9x."

should read:

"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on XP, NT, ME, and 2000, and the System directory on 9x."

Also, if you need to have the ocx file in different directories depending on the operating system (XP or 2000), you will just need to make two versions of the exe. A WinXP version and a Win2000 version.

Hope this helps!

Travis H.
National Instruments

[Radman]

Travis,

I am still a little confused....All I am trying to do is to make a self-executable 3D plotter that allows me to change things like the scale, titles, etc. I did find a way to use property nodes to bypass this but I am still interested in why the example didn't work. Here are the steps I followed:

In application builder
1) insert the cw3Dgraph.ocx as a source file
2) Use the advanced tab and have the program insert the file in the c:\windows\ssystem32 folder (I confirmed the installer did this)
Outside application builder
3) I registered the .ocx file externally using start>>run>>reg32 c:\windows\system32\cw3dgraph.ocx (when hitting enter the system confirmed that the .ocx file was registered on the computer).

Run executable....I could make 3D graphs, rotate the plot but I could not change the x,y,z scales or anything like that.
Am I missing something here?

Thanks for your help.....

Radman

---

@Travs H. wrote:
Hi Radman!


Maybe Robert will have more to add, but I'll throw in my 2 cents worth 🙂

When creating an executable/installer, setting Top-level VIs is what designates what VIs actually open and run when you double-click your exe file. By adding both the DS 3D Graph Reader & Writer as Top-Level VIs, you are indicating that when running the executable you want both of those VIs to automatically open and run.

Now about your concern for the batch file. This document was originally created before the release of Windows XP. With that being said the following:

"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on NT, ME, and 2000, and the System directory on 9x."

should read:

"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on XP, NT, ME, and 2000, and the System directory on 9x."

Also, if you need to have the ocx file in different directories depending on the operating system (XP or 2000), you will just need to make two versions of the exe. A WinXP version and a Win2000 version.

Hope this helps!

Travis H.
National Instruments

---

[Joe_Guo]

try double click or right click on the 3D graph, it should bring up a dialog box with all the properties. Youc an adjust the scales from there.

As it for the ocx, if you selected to build an installer and checked the 3D graph entry, then there is no need to worry about where the ocx will be put and how it will be registered. The installer handles all these for you automatically.

-Joe