11-09-2010 11:43 AM
I am trying to utilize the new 3D graph for labview 2009, and all my testing works fine.
However, as soon as I integrate it into my main application, everything goes wonky.
Whenever the graph is not the selected item, IE whenever I click anywhere else, the graph becomes see through.
I can see through the current tab to the one directly below it.
As interesting as a Feature as this is, I really just want the 3D graph.
Has anyone experienced anything similar?
11-10-2010 04:55 PM
Hi Ben,
I haven't seen or heard of this happening before. Can you post the VI that's showing this behavior? I'd like to try to reproduce it here.
11-11-2010 04:29 PM
Andy,
We could potentially send a set of VI's to NI for diagnosis, but this is part of a very large project. We've tried reproducing the issue in a simpler example, but so far we haven't been able to.
I posted a question on this before: http://forums.ni.com/t5/LabVIEW/3D-graph-issues-in-8-6/m-p/983248 but go no response then.
To better explain, we have attached an image of our top-levle program with the 3D graph display corrupted. The 3D graph is a square near the upper right which we've outlined in red. This should show a white graph with axes, but instead it shows what you would see if you pressed the Setup tab. Note that within the tab labeled (0)AIMMS20, the full tab is occuppied by a sub-panel container which has a .vit loaded. In this case, the graphical error is showing what is on another main tab of the top program.
When we open the .vit directly in editing mode, we can see a similar effect where the 3D graph shows whatever is behind it in Windows, even when it is not running.
We made a simple example with a 3D graph on the front panel. We could not generate the error then. We then put that VI in a sub-panel container on a tab of another VI, but still could not generate the problem. We also tried several computers and LV versions 8.6, 2009, and 2010. In all cases, the problem is readily apparent in our large program but not in the example. Apparently the problem has to do with something subtle in our large program, but so far we have not been able to identify what.
Any ideas would be appreciated.
Regards,
DaveT
11-12-2010 03:57 PM - edited 11-12-2010 04:05 PM
Hi Dave,
I'm a little confused by the end of your note there ("In all cases, the problem is readily apparent in our large program but not in the example"). Do you mean that you've tried your large program in all of those versions of LabVIEW (8.6, 2009, 2010) and seen the same behavior, or just that you weren't able to reproduce the issue with your example in any version?
If the main VI does show this in any version, then I'd certainly be interested in taking a look and trying to reproduce it here.
11-12-2010 04:20 PM
Andy,
What I meant was that we have seen the bad behaviour in our big VI in all those versions of LV. We've only worked on trying to create a simple example in 2009. So far no luck reproducing it.
For now, we have moved on by replacing the native 3D graph with the older ActiveX version. Our code is now working pretty well, so we're reluctant to take the time to create a package that you could use to test it. This would be a large download that I would want to send directly to you. We can't put it on a public forum. If we were to send it to you, how can we get it to you?
DaveT
11-17-2010 03:05 PM
Hi Dave,
Check your private message inbox.