[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] context attribute to allow control anti-aliasing more finely?



----- Original Message -----
> >
> > ----- Original Message -----
> >> On Jan 7, 2011, at 6:49 AM, Benoit Jacob wrote:
> >>
> >> >
> >> > Hi,
> >> >
> >> > We currently have a boolean 'antialias' context attribute. But it
> >> > doesn't allow to control the quality of the anti-aliasing.
> >> >
> >> > Should we:
> >> > * not do anything about it?
> >> > * or replace it by an integer with 3 possible values, say "none",
> >> > "low", "high" ?
> >> > * or, to keep compatibility with existing WebGL code, add a
> >> > separate
> >> > 'antialiasfactor' attribute?
> >>
> >> We did it this way to make things simple. I think we should leave
> >> it
> >> as is for 1.0. But improving it in the future is certainly
> >> possible.
> >
> > OK. Maybe then we should at least consider using similar
> > antialiasing
> > settings. AFAIK Mozilla uses the default. I've had a user reporting
> > that
> > the rendering in Chromium looked different. Could you please point
> > me to
> > where it's implemented in WebKit?
> >
> > Benoit
> 
> Certainly on my Win7 machine, I get antialiassing in Chrome - but not
> in
> Firefox.

Are you sure you get no antialiasing at all in Firefox, or might you be getting some very cheap antialiasing, like only 2 samples per pixel?

Benoit

> 
> -- Steve
-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------