Date: Mon, 17 Jun 2019 20:31:27 -0400
I can only imagine that mouse/touch input needs to be in the same coordinate system as the drawing.
Sent from my BlackBerry portable Babbage Device
| From: Rene Rivera via SG13 Sent: Monday, June 17, 2019 7:08 PM To: sg13_at_[hidden] Reply To: sg13_at_[hidden] Cc: Rene Rivera Subject: Re: [SG13] 2D graphics for Cologne - P0267R9 |
On Mon, Jun 17, 2019 at 12:42 PM Michael McLaughlin via SG13 <sg13_at_[hidden]> wrote:
The next revision of 2D graphics will be presented at the upcoming Cologne meeting. As opposed to making everyone wait for the mailing, if you would like, you can access R9, the paper submitted for the pre-meeting mailing, here: https://github.com/cpp-io2d/io2dts/blob/master/papers/P0267R9.pdf .
Even though I'm still reading the paper I feel I should point out something that struct me in the "Introduction", while reading this statement:
"...the design of an input API is inherently reliant on the design of the output API..."
and how it's used as a justification "to only pursue of the input API after the output API design was complete." In my experience I don't see any truth in that statement no matter how hard I try to think about it. Maybe my experience in the user interaction field is limited, but I can't remember a case where a rendering, i.e. output, API was required for the input. Can you provide some reference material to support your claim in this respect?
Received on 2019-06-17 19:33:17