What i'm referring to is the locale implementations, here's what I found today and dont find any explanation yet rather than theres a bug, or they left this area unfinished...
1. Setting the default Swing Locale to Spanish rather than my english Locale, when my program starts up and then later shows a JFrame, when the user closes the JFrame I show a plain JOptionPane just passing a string to it.. the default Title of the optionpane is not reflected by the spanish Locale, however everything else on my JFrame was. So in the initialisation of the JFrame I performed a this.setLocale(spanishLocale); Which then solves the problem for the JOptionPane. Surely it should have inherited the default locale that was set, I shouldnt have to set it again for the container :|
2. The JOptionPane itself.. Why oh Why do we have to supply our own locale properties for the yes/no buttons etc.. They have gone halfway and done everything for other components so why leave out the optionpane buttons ? That just seems a bit of a half arsed job to me :-(
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum