<off-topic> > > Whenever we schedule meetings, we always allot the first 20 minutes to > discussing a great idea, and then we spend the other 40 minutes > devising evil schemes. We always end meetings with a hearty round of > diabolical laughter. >
I don't think I've laughed so hard at work in... well, ever. :) Unfortunately, here we don't have diabolical laughter mastered yet. It's more of a bewildered/confused/incredulous kind of laughter. </off-topic> Seriously though, Sun does have a lot of power to make relatively-inconsequential users/developers quake with fear. Just the fact that there are still whole software systems built around 1.3.1 or earlier releases is a testament to the distrust by many software systems engineers. I don't mean this as a criticism at all, just an observation of people's conceptions about Java. For myself, I was one of the first on my team to install 1.5b1 and I was proud of the fact... until it fragged my system. Something involving the new Java plug-in control panel not allowing me to choose a 1.4 JRE I think. I'll have to reinstall and investigate what was going on there. (Some of us like being on the bleeding edge, with all its pain... :) ) > You can programmatically set the system property (via > System.setProperty) in your app at startup. But I highly discourage > you from doing so, for the same reasons that we haven't > enabled the OGL > pipeline in the first place. But assuming your app has some kind of user profile/preferences mechanism, you could allow the user to choose whether they want to enable the high-performance* mode or not, then save that setting and use it early in your app startup to set the system property... just a thought. Mike Nidel * not a guarantee =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
