Confirmed users
138
edits
| Line 278: | Line 278: | ||
''We should also provide shortcuts that correspond to canvas-2D operations.'' This will offer maximum efficiency, so we don't have to spend cycles detecting special cases when the caller code already knows what the special case is. | ''We should also provide shortcuts that correspond to canvas-2D operations.'' This will offer maximum efficiency, so we don't have to spend cycles detecting special cases when the caller code already knows what the special case is. | ||
Bas: So, obvious cases here I believe are covered here much like Direct2D does 'DrawRect' 'FillRect' 'DrawImage' etc. In for example the rectangle (and possibly ellipse, etc.) case this also allows us to reuse vertex buffers which already have the correct tessellations and such, since these are very common in general, not just in Canvas2D. | Bas: So, obvious cases here I believe are covered here much like Direct2D does 'DrawRect' 'FillRect' 'DrawImage' etc. In for example the rectangle (and possibly ellipse, etc.) case this also allows us to reuse vertex buffers which already have the correct tessellations and such, since these are very common in general, not just in Canvas2D. As stated above, I think the Path stuff is a very bad idea. | ||
enum ClockDirection { CLOCKWISE, ANTICLOCKWISE }; | enum ClockDirection { CLOCKWISE, ANTICLOCKWISE }; | ||