We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
IndexProgramming Questions & HelpSyntax Questions › Different Codebase for Tiger vs. Leopard
Page Index Toggle Pages: 1
Different Codebase for Tiger vs. Leopard? (Read 238 times)
Different Codebase for Tiger vs. Leopard?
Dec 11th, 2008, 6:41am
 
(This isn't really a syntax question per se, but there didn't seem to be a better place to post it)

For some reason, I get different results when I'm using beginShape() with the default 2D renderer on an Intel (C2D) machine running Leopard, than when I use it on a PowerPC (G4) running Tiger.

I'm drawing a line made up of many points a distance of one pixel apart. When I run it on my Intel machine, it produces a jagged line, like so: http://dlpart.com/images/jaggy.png. When it runs on my PowerPC machine, it's nice and smooth, like so: http://dlpart.com/images/smooth.png.

What's going on here? Are there two different codebases for the PowerPC and Universal versions? Is it a Leopard/Tiger difference? Is this some bug that was later corrected? I'm using the 148 Beta release, rather than 1.0.
Re: Different Codebase for Tiger vs. Leopard?
Reply #1 - Dec 11th, 2008, 11:43am
 
FYI, such question belong more to the integration forum, I think.
And yes, leopard and tiger are indeed different beasts!
But zoological considerations aside, I see you have also different hardware, so probably different graphic cards, probably different drivers, etc.
Re: Different Codebase for Tiger vs. Leopard?
Reply #2 - Dec 11th, 2008, 12:44pm
 
I'm aware that Tiger and Leopard are different, but that does not necessarily mean that the same program will behave differently between the two.

As for hardware, it's my understanding that the purpose of standard renderers such as Java2D are to mask the differences in hardware between any two computers, so one doesn't have to worry about the specific hardware configuration. Furthermore, if anything, I would expect it to look better on the more recent C2D machine. which has a Radeon X1600 (it's a late-2006 MBP), rather than the G4, which has a decrepit GeForce 2 MX (2001 Quicksilver), but it's the other way around.
Re: Different Codebase for Tiger vs. Leopard?
Reply #3 - Dec 11th, 2008, 8:07pm
 
Processing does not use a different code base between Tiger and Leopard, however Apple's Java is quite different between the two and was largely rewritten. So any differences are likely the result of those changes.
Page Index Toggle Pages: 1