W3C home > Mailing lists > Public > public-canvas-api@w3.org > April to June 2014

Bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=13277

From: Jay Munro <jaymunro@microsoft.com>
Date: Fri, 20 Jun 2014 22:30:48 +0000
To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Message-ID: <63ba1baf7bbc406790405ec0aaf8da55@BY2PR03MB521.namprd03.prod.outlook.com>
I've been looking at old Level 2 bugs, and this one sounded interesting. The idea of a getter to get the current "from" point when using moveTo, lineTo, or arcTo. From an implementation standpoint, how difficult would it be to cache the current path's x/y location? 

I could see this several ways: 

//  System current path point
readonly attribute double  context2d.currentPointX;
readonly attribute double  context2d.currentPointY;

// Path2D current point
readonly attribute double  Path2D.currentPointX;
readonly attribute double  Path2D.currentPointY; 


Jay Munro  Content Developer 2 Internet Explorer     85/2275    425-703-2242 
Received on Friday, 20 June 2014 22:31:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:57 UTC