"range" property in PathWrap should be tested or removed/hidden

[tkuchida]

From PathWrap.h L65:

// TODO Range should not be exposed as far as one can tell, since all instances
// are (-1, -1), which is the default value, and that means the PathWrap is
// ignoring/overwriting this property anyways.
OpenSim_DECLARE_LIST_PROPERTY_SIZE(range, int, 2,
    "The range of indices to use to compute the path over the wrap object.")

Issue arose on the Forum (topic 7826).

[chrisdembia]

Only the ancient creators know the hidden use of this mysterious property.

[tkuchida]

Looks like getStartPoint() and getEndPoint() are used in GeometryPath::applyWrapObjects() (and elsewhere). PathWrap::getStartPoint() returns get_range(0), so the range property may be used after all. Recommend investigating and either adding test case or removing the property.