Might I suggest nodecount.PathBench
I bring it up because Path performance is costly for my app, when it represents
a fraction of the number of pixels rendered. I.e. it could use some attention
and with a test app like these at least you will know when things are going in
the right direction
I agree. In fact, the Button cases which end up not being pixel snapped cause
huge performance loss (run ButtonBench on desktop). If you whip up a quick file
I'll add it in (I'm busy at the moment chasing down scrolling button
performance issues…).
The shadow issue I'm not sure about --
