FAQ
You can do that, in fact the x/image/draw package has code to do it.
But it is expensive on a CPU and effectively free on a GPU, so shiny
screen drivers pass the matrix to the OS in some form so it can get to
the GPU.
On Thu, Apr 21, 2016 at 9:31 AM, Dave MacFarlane wrote:
I'm not sure I follow why that's going to be a problem. Isn't the
transformation matrix already calculated and provided as a parameter to
draw? Why is that going to be more complicated than just multiplying it
through?
On Wed, Apr 20, 2016 at 11:29 PM, Nigel Tao wrote:

On Wed, Apr 20, 2016 at 8:51 AM, Dave MacFarlane <driusan@gmail.com>
wrote:
3. Use /dev/draw/new for NewTexture/NewWindow, make Upload/Publish
wrappers
around /dev/draw/n/ctl. Make NewBuffer() a thin wrapper around
*image.RGBA
What's your plan for implementing affine transformations (including
scales and rotations)? The screen.Drawer interface isn't limited to
1:1 copies.



--
- Dave

--
You received this message because you are subscribed to the Google Groups
"golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 10 of 11 | next ›
Discussion Overview
groupgolang-dev @
categoriesgo
postedApr 19, '16 at 10:56p
activeApr 21, '16 at 3:41p
posts11
users6
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase