get positionWorld or just position from Markups?

[mauigna06]

While reading a markups nodes control point position for use in the Dynamic Modeler, which function should be used from the ones below:

markupsFiducialNode->GetNthControlPointPosition(0, mypoint);

OR

markupsFiducialNode->GetNthControlPointPositionWorld(0, mypoint);

[mauigna06]

Following what is done in one of the first DynamicModeler's tools:

SlicerSurfaceToolbox/DynamicModeler/Logic/vtkSlicerDynamicModelerPlaneCutTool.cxx

Lines 327 to 328 in e8b8f70

	inputPlaneNode->GetOriginWorld(origin_World);
	inputPlaneNode->GetNormalWorld(normal_World);

These are the functions that would need to be changed to their World counterpart

AddControlPoint
GetAxes
GetAxis
GetXAxis
GetYAxis
GetZAxis
GetBounds
GetCenter
GetCenterOfRotation
GetClosestControlPointIndexToPosition
GetControlPointPositions
GetCurvePoints
GetImplicitFunction
GetNormal
GetNthControlPointNormal
GetNthControlPointOrientationMatrix
GetNthControlPointPosition
GetNthControlPointPositionOrientation
GetOrigin
GetPlaneCornerPoints
GetSize
InsertControlPoint
IsPointInROI 
SetAxes
SetCenter
SetCenterOfRotation
SetClosestControlPointIndexToPosition
SetControlPointPositions
SetCurvePoints
SetNormal
SetNthControlPointNormal
SetNthControlPointOrientationMatrix
SetNthControlPointPosition
SetNthControlPointPositionOrientation
SetNthFiducialPosition
SetOrigin
SetSize

@lassoan, should this be done to all dynamic modeler tools?

[lassoan]

In general, we transform all the inputs to the world coordinate system, perform the operation there, then transform the results to the output model's coordinate system. So, you don't have to use any of the Get...World convenience methods. However, if a Get...World method is available then usually it is preferable to use it (they may return cached values instead of recomputing transformed values).