3D Graph D&D behavior

[Florian.Ludwig]

Hi,

Im a little lost: I can't find the properties to change the drag and drop behavior for pan and zoom for the 3D graphs I am using.

I'd like them to respond to user inputs in the same way, unfortunately it's currently like that:

3D Curve

• rotate: ctrl + left click (lc)
• pan: shift+lc
• zoom: alt+lc

3D Waterfall

• rotate: lc
• pan: ctrl+lc
• zoom: shift+lc

Why it would be preconfigured so inconsistently is beyond me.

Is there anything I can do about this?

Best regards,

Florian

[NinaM]

Hi Florian,

could you please tell me, what kind of VI´s you are using?

Which LV version do you have?

Best regards,

Nina

[Florian.Ludwig]

Should have thought of this:

LV-Version: 12.0.1f5 (32-Bit), german

VIs:

1. Waterfall: 3D Waterfall Datatype.lvclass: Plot Helper.vi (added whitespace between ":" and "P" not to make a funny face)
   Is added automatically when you drop The Graph to the FP form:
   Modern -> Graph -> 3D-Graph -> Waterfall
2. 3D Curve:NI_3dgraph.lvlib:3D Curve.vi
   Added in the BD from:
   Programming -> Audio/Grafik -> 3D-Graph -> 3D Curve

Best regards

Florian

[NinaM]

Hello Florian,

There are a couple differences between the 3D Waterfall Graph.VI and the 3D Curve Graph (ActiveX).VI
 
The first difference that I would point you towards is the way that these indicators are coded, the 3D waterfall takes in a lvclass data type and is coded using object oriented programming, where the 3D Curve Graph is using activeX invoke and property nodes to wire the control.
 
The root of this issue is that these are two completely different controls and they are expected to behave differently. If you take a look at every other 3D control in the Modern>>Graph>>3D Graph Palette you can see that they all operate the same as the 3D Waterfall Graph.vi
 
The 3D Curve Graph (ActiveX).VI is using an older implementation of the 3D graph that relies on ActiveX, and does not have the same shortcuts.
 
 
So in brief, these operate differently because they are different indicators. The recommended indicators would be the updated 3D picture Controls instead of using the ActiveX implementations. Here is a KnowledgeBase Article that mentions that the ActiveX controls are a legacy control and that the newer controls are recommended.

Where Can I Find Examples for the Legacy 3D Graph ActiveX Control?

http://digital.ni.com/public.nsf/allkb/1537924B6AF6278386257B15007E5CCE?OpenDocument

I hope, this is is helpful for you.

Best regards,

Nina

[Florian.Ludwig]

Hello Nina,

thanks for answering.

It clears up the reasons, but it helps only a little as there is no simple way to remedy the situation.

I had to make an ugly hack to get the pan operation to work halfway OK for the waterfall plot anyhow.
Your answer does point me to a solution: Replacing the waterfall plot with the "legacy" implementation that may actually work.

I don't have time to do that just now though. Maybe I can make another hack - something with filter events maybe.

I must also state that I don't expect new implementations for the same problem to behave differently in the way the new 3D plots do:

Remapping control keys so that not only the programmer but even the end user can tell these plots don't belong in the same application.

For your reference a result of my initial search that also gave me an idea how to fix pan:

http://forums.ni.com/t5/LabVIEW/My-Big-Book-of-Grievances-and-Bugs-concerning-the-new-3D-Surface/m-p...

Best regards,

Florian