I'm suspicious it wont actually work, given you dont mention OS X's timing problems
which are conisderably worse than win XP
I've never heard of any timing problems on OS X.
Using this simple test program:
public class Main
public static void main(String args) throws InterruptedException
long start = System.currentTimeMillis();
long then = start;
System.out.println("---- System.currentTimeMillis() Resolution Test ----");
long now = System.currentTimeMillis();
if (now != then)
then = now;
} while ((then - start) < 10000);
System.out.println("---- Sleep Test ----");
start = System.currentTimeMillis();
for(int i = 0; i < 10000;i++)
System.out.println("10000 * Thread.sleep(1) caused a delay of "+(System.currentTimeMillis()-start)+"ms");
Timer resolution of System.currentTimeMillis() is 16 ms on Windows XP and 1 ms on OS X.
Thread.sleep(1) 10000 times delays 19531ms on Win XP.
Thread.sleep(1) 10000 times delays 10274ms on OS X.
So I don't understand what you are referring to whenyou claim OS X has worse timing problems than Win XP.
but we'll see how it goes. I can always force that to nanotime, since java2d doesn't work on OS X with less than 1.4 anyway (PNG's don't load, for instance.
There was a release of Java 1.4 that swapped red and blue for some PNGs (those with alpha channels) on OS X, that was later fixed. It is certainly false to say that PNGs in general don't load - I use them all the time without problems.
Thankfully you can mostly count on 1.5 being installed these days (anyone who downloads the auto OS updates will have it)
Well at least you got one thing right