Community
Participate
Working Groups
setAntialias is missed on GC. But currently we always render antialiased graphics on the client. So, I would suggest to implement this method empty. This would increase the single sourcing capabilities of the GC.
There are three antialias modes - SWT.DEFAULT, SWT.OFF, SWT.ON. Implementing GC#setAntialias(int) method as NOP will break it, as SWT.OFF mode will not turn off the antialiasing. There is no problem with GC#getAntialias() to always return SWT.DEFAULT or SWT.ON.
I think, for the sake of single-sourcing, we should ignore that fact that antialiasing cannot be turned off. The same applies to GC#setTextAntialias(). Any objections?
(In reply to comment #2) > I think, for the sake of single-sourcing, we should ignore that fact that > antialiasing cannot be turned off. The same applies to GC#setTextAntialias(). > Any objections? +1
Introduced get/setAntialias(), get/setTextAntialias() on GC. Changes are in CVS HEAD.