jonlipsky

@wjk The way that I handle that use case with this library in my own apps is that the base implementation draws at full DPI, and then I wrap that...

@vpenades The original intent of CanvasState is so that we can store values (sometimes differing on a per-platform basis) so that we can make sure that SaveState() and RestoreState() behave...

I agree, those are all good changes and make for a more general purpose library. For my use cases, which are 100% in the minority, where I need that level...

@vpenades Yes! That would be greatly appreciated.

This adds a significant performance and memory hit. The library should be able to re-use the underlying native image representations, especially when you need to do something like tile an...

@hartez @jsuarezruiz This will need a more involved fix. The problem is that with Direct2D you have limitations about using resources between contexts. In some cases, the proposed solution would...

I'll need to investigate this, as in my own personal code base this works on Android, so I need to figure out what changed when I extracted this code out.

Great call out. I don't support Shear in TouchDraw, which is why I never added that. I'll add that to the to-do list.

@mattleibow I'll add that to my to-do list.

@537mfb Yes, I'd be happy to submit an update to the pull request to change the naming of `RightHeader` back to `Header`. I renamed that property because the original behavior...