3D Coordinate Conversion VI

[Standardnutzer]

Add a description of inputs and outputs relative the the chosen polymorphic instance of the VI.

Current documentation is Axis 1, Axis 2, Axis 3 and there is no description e.g. how those names correlate to the polar coordinates Phi, Theta and length!

I had to figure it out by trying - please just add tose few lines to the Labview help!

[AristosQueue (NI)]

The image shows that P(x, y, z) cartesian maps to P(rho, theta, z) cylindrical and to P(rad, theta, phi) spherical. But you are correct, putting that in text would be helpful. I will file the CAR to update the documentation.

[Darren]

Moved to CAR database: CAR 503133

[Standardnutzer]

Does that mean that someone will add the information to the documentation or is this 'declined'?

[Darren]

The CAR database is used internally at NI to track bug reports. Whenever we move something from the idea exchange to the CAR database, we mark the idea as "Declined" since we're tracking it with this other mechanism. I wish we had a "Moved to CAR" status in the Idea Exchange, but since we don't, "Declined" is what we've historically used in this situation.

[Standardnutzer]

The documentation of LabView 2016 still doesn't mention how spherical coordinates to the connectors of the VI ...

[X.]

CAR = Crutzmuch Antigravity Remobulator.

In short, there is really no telling what's going to happen to the thing, but keep bugging the little blue guys, they might eventually do something about it.

[Darren]

The issue is still being evaluated for a future LabVIEW release. I'll let the documentation team know that y'all were asking about it.

[JayLiu]

Thanks for the follow-up, Standardnutzer! We have been prioritizing our documentation tasks for each release, and sorry that this issue hasn't been fixed yet. It's in our backlog.

[Standardnutzer]

It doesn't show up in LV2017 either

[Darren]

The issue has been fixed in LabVIEW NXG documentation, but not yet in LabVIEW documentation. I have once again pointed the documentation team to this thread.