Why is 'MatrixOrderPrepend' the default transformation order in GDI+? -


i had modify mfc app pretty graphics (simulate lcd display). not home turf managed solve gdi+; graphicspath, bezier curves , matrix transformations friends. struck me odd matrix transformation operations seem backwards default.

if like...

graphics g; g.translatetransform( ... ) g.rotatetransform( ...) s.scaletransform( ... ) 

...then transformations applied opposite order: scale, rotate, translate. counterintuitive me.

i know can add parameter transform calls change behaviour want, this:

g.rotatetransform( ..., matrixorderappend) g.scaletransform( ..., matrixorderappend) 

what rationale having matrixorderprepend default?

on msdn short article why transformation order significant. i'm not sure why 'matrixorderprepend' default value, either have valid applications. guess had pick one, wouldn't worry !


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -