Version 0.3 of iRATE radio is just now being released, but the Mac OS X version that is built using Eclipse's SWT toolkit is being held up a couple days because I found a bug.
But a test build has been posted on iRATE's unstable downloads page. As long as you read the ReadMe file, you shouldn't have any trouble. It's working well enough to be useful and enjoyable.
It would be very helpful to me to get some more widespread testing, because the OS X SWT version hasn't been tested by anyone but myself so far. (Previously iRATE for OS X was only available in the version built with Swing).
It's likely that there are some other bugs that I could fix before the release, if only I knew about them.
Thanks for your help.
Want to Use SWT in OS X?
If you try to use SWT's OS X build you are likely to think it's not really ready for use. It will seem as if your user interface is really brain-damaged. But that's not really the case.
The reason is that SWT uses native widgets, sorta like AWT does. For OS X, it makes calls to Carbon. This is done by supplying a dynamically loaded native code library for each platform and widget set, that is loaded via the Java Native Interface.
The way Java applications are built in application bundles on OS X (to make a program you can run by double-clicking it) has the threads set up wrong for the native widgets to be able to process the events.
What you need to do is read the instructions in Eclipse Bug #40003.
In short, what you need to do is use an executable called java_swt instead of Apple's JavaApplicationStub. Both these programs launch the Java VM and tell it to run your java jar, but java_swt will set up the threads to make SWT happy.
I thought I should post this here so someone with the same trouble I had will find it with Google. It's a simple solution but apparently not too well known yet.