Yes princec, but there could be some “political” reasons for not enabling it by default.
Nothing political at all… openGL doesn’t work on about 35% of the Windows machines out there.
Cas 
Maybe using a fallback mode at runtime: no good opengl ? goto software implementation.
Maybe we’re simplifying a complex problem…
[quote]Um… No, the next release, not 1.5. Again - this is regarding the (even more) optimized through SSE/MMX software loops, not WGL pipeline
[/quote]
Ok… just to be clear is that, “not 1.5” but 1.5.x where x>0, or 1.x where x>5 ??
It will be in the next ‘rand(MarketingStuff)’ version.
[quote]It will be in the next ‘rand(MarketingStuff)’ version.
[/quote]
Crap.
Well feel free to whine at someone resposible for defining the magnitude of ‘MarketingStuff’ on my behalf about this :). It is so long over due.
No matter what argument you give rand it always seems to return a number between 0 and 1…
Cas
Thak makes me think that the loops are up and running but someone in the marketing is holding them for better times.
I already saw a sad story about technology and marketing some time ago. Do you remember the Amiga 3000+ ?
The managers were conviced it was too advanced for the market at that time. So they pushed the Amiga 600…
So to summarize,
the ogl pipeline will not be available in beta 2 at all?
Or it will be availabel in beta 2 but not turned on by default?
Or the ogl pipeline in windows won’t be available until 1.5.1 beta 1?
You guys have me confused…
Do not worry nonnus, OpenGL Java2D acceleration WILL be available in b2/Win (it’s already there in b1/Linux).
Enhanced software loops (MMX/SSE blitting, alphacompositing, etc) WILL NOT be there and we don’t know when they’ll be available to the rest of us.
Mik of ClassX
[quote] No matter what argument you give rand it always seems to return a number between 0 and 1…
[/quote]
“In the time of war the value of sin() may reach up to 4.”
©military joke