Please see this search of "Ben 3D" for everything I have said about the 3d graph.
1) Try to keep the properties screen format matching up with property/method structure. It make it easy to figure out how to code.
2) Color for CW 3d graph is BGR rather than RGB. This confuses people.
3) THe CW Graph ned a legend
4) Stacks of multiple slice rendered as multiple plots are nice for MRI type images. Large data sets and many slices can make PC scream for help. My Mouse Tendo images can take 1/2 an hour to update the screen. can we speed this up?
5) Transparency is way cool! don't loose that!
6) If you play around really hard with the CW 3d graph you will find that there is one type of rotation you just can't do. I resort to rearranging my axis if I run into this issue.
7) Let use set properties while the code is running. Now we have to stop the app to get at the property screen. So we have to code everything or don't offer it.
😎 I like how the 3D graph can be used inside an ActiveX container inside Excel etc. Don't loose that one.
9) I'd like to be able to render an image either on a a surface without having to bend over backwards to handle how too many pixesl to a small surface end up all showing up as pink-brown. I have two needs for that. 1) My train layout and 2) Show the flight path of a weapon over the ground.
9a) What I would have done if it was quick and easy... to show airflow velocities, magnitude and direction in 3D I was concidering rendering a 3d quiver (arrow) at the location a air speed was measured and render that arrow on a surface where the color implies the magnitude. Since it required a bit of work and the data was getting massaged again after it left my app, that work was never completed.
I'll post other ideas as they come up latter.
3D picture
10) Confesion: I have not used it since it moved out of the public beta.
11) I was disappointed it only supported 300X600 or something so small it was useless. I think the newer version supported larger so that is a non-issue I hope.
12) I wrote a "3D hierachy"* for the public beta version needed the ability to skin the object AND support shadows. The skins in this case where LV icons on the cube representing each VI. When I get back to this project (I really think it will help with LVOOP where large apps get really crazy), I'd like to have shading (skins plus shading supported now?).
13) Noe that Scripting is leagal, it is only a matter of time until we try to implement a 3d diagram. Maybe give some thought to what it would look like and what we would need to implement same (Whci object did he click on?)
Just dumping my brain to hopefully inspire others to do the same.
Ben
* Ask Todd Seier about his frist day as a platinum support engineer.
