I'v returned to my OS X code after an absence to find its "stopped working". Iv upgraded to the latest version of JOGL - a good idea anyway, but I'm getting the same error. I'v tried to eliminate environmental issues before posting. I think something weird with OS X is going on as it was working fine several months ago.
My NEWT setup code is pretty standard (it was based on an example).
Yeah, thats the weird thing. My last code revision was working fine. The only thing that has changed is time. So I'm thinking it's something specific to my system. A software update or some such. I try not to post with "hey it's broken" questions as its usually something I can debug myself. But this one is weird. Especially since I'm getting the same results with the older version of JOGL (not sure which one, but it's the old package structure). So i forked my project and updated to the current version of JOGL. Same result. I guess I'll work through some NEWT examples and see if they fail in the same way.
I'v been using -XstartOnFirstThread of course.
I'v boiled it down to breaking on window.setVisable(true) with NSInternalInconsistencyException
OK, I'v isolated to an interaction with AWT. Before setting up the NEWT window I load some images with AWT and convert them to JOGL images. This had always worked just fine. I'v always set java.awt.headless=true. In this case its still kicking in and interfering with JOGL.
I don't recall an OS X Java update recently. Unless it's deciding to use hardware because of some other metric I don't know about. Or it was just some random timing / side effect.
Anyway, so that answers the question... kind of :)
Yeah, I'v worked out that was the problem. The thing that threw me was that I was definitely loading my images before setting up NEWT windows and it was working. I guess it was always waiting to fail on me :).
I know it was in that order because of my source history and because now my NEWT window is grey for a few seconds while it does the AWT stuff. I didn't have that before.
Anyway, a problem solved is... a.. problem solved? :)
oh i totally agree.. thats why i was so perplexed about why it seemed to stop working with no code changes. there is always the risk it fails after a project is packaged and released. or it works for me but fails for other people and i never know about it.