[API REVIEW] RT-30171: 3D versions of localToScreen and screenToLocal

[Richard Bair]

What's the JIRA issue so I can mark it?

On May 2, 2013, at 11:15 PM, Pavel Safrata <pavel.safrata at oracle.com> wrote:

> These methods were not released yet so we would not break compatibility with anything except of several weekly builds back.
> Anyway, I agree with Richard's proposal.
> Pavel
> 
> On 3.5.2013 0:02, Ali Ebrahimi wrote:
>> +1.
>> Breaking (source & binary)compatibility is not good thing.
>> 
>> 
>> On Fri, May 3, 2013 at 2:21 AM, Richard Bair <richard.bair at oracle.com> wrote:
>> Hi Pavel,
>> 
>> > // these two already exist:
>> > public Point2D localToScreen(double localX, double localY)
>> > public Point2D localToScreen(Point2D localPoint)
>> > // these two exist but without the 2D suffix, so rename them (they were added in FX8 so no backward incompatibility):
>> > public Point2D screenToLocal2D(double screenX, double screenY)
>> > public Point2D screenToLocal2D(Point2D screenPoint)
>> > // add these four for 3D
>> > public Point2D localToScreen(double localX, double localY, double localZ)
>> > public Point2D localToScreen(Point3D localPoint)
>> > public Point3D screenToLocal3D(double screenX, double screenY)
>> > public Point3D screenToLocal3D(Point2D screenPoint)
>> 
>> Just mulling it over. What about:
>> 
>> // these two already exist:
>> public Point2D localToScreen(double localX, double localY)
>> public Point2D localToScreen(Point2D localPoint)
>> public Point2D screenToLocal(double screenX, double screenY)
>> public Point2D screenToLocal(Point2D screenPoint)
>> public Point2D localToScreen(double localX, double localY, double localZ)
>> public Point2D localToScreen(Point3D localPoint)
>> public Point3D screenToLocal3D(double screenX, double screenY)
>> public Point3D screenToLocal3D(Point2D screenPoint)
>> 
>> In this case we only append the "3D" to screenToLocal variants that produce Point3D?
>> 
>