That sounds like a good plan. Hopefully the resulting webrev will be
short and sweet and easy to verify.
We still leave on the table any convenient way for a developer to get
auto-scaled-double-buffering without going through these same pains in
their own code, but hopefully everyone relies o
Hi, Anton.
Please check performance w/o buffers too, to know the difference.
On 13.12.2013 22:13, Anton V. Tarasov wrote:
Summarizing your comments. We can't export a scaled version of a
BufferedImage in the bounds of the current API without violating the
spec. Unless a scaled BufferedImage is
On 12/13/13 2:05 AM, Anthony Petrov wrote:
On 12/12/2013 07:18 PM, Anton V. Tarasov wrote:
[cc'ing to j2d alias]
On 11.12.2013 21:29, Sergey Bylokhov wrote:
On 11.12.2013 20:23, Anton V. Tarasov wrote:
- CGraphicsDevice
This setter is only called from
CPlatformLWView.getGraphicsDevice(). I
Summarizing your comments. We can't export a scaled version of a
BufferedImage in the bounds of the current API without violating the
spec. Unless a scaled BufferedImage is used internally, in which case we
are less constrained. Ok, let's try this approach. I searched the code
for all the cases
