Odd UI behavior running JME 2.0 HelloWorld under Eclipse (on Mac)

Troubleshooting General Help
1

I am getting some odd behavior running JME 2.0 HelloWorld under Eclipse (Ganyamede) on Mac.  I get the odd error messages below and the JME window comes up with grey block, but I cannot interact with it using the mouse or keys (all I get is a spinning beachball on the JME window).  However, if I just run this outside Eclipse, it is fine.  Has anyone else seen this behavior, or have a suggestion?



Tx, -CR



2009-03-08 19:22:48.093 java[31539:10b] [Java CocoaComponent compatibility mode]: Enabled

2009-03-08 19:22:48.095 java[31539:10b] [Java CocoaComponent compatibility mode]: Setting timeout for SWT

to 0.100000

2009-03-08 19:22:48.715 java[31539:16703] *** -[NSConditionLock unlock]: lock (<NSConditionLock: 0x1282b6

ce0> '(null)') unlocked when not locked

2009-03-08 19:22:48.716 java[31539:16703] *** Break on _NSLockError() to debug.

2009-03-08 19:22:48.818 java[31539:16703] *** -[NSConditionLock unlock]: lock (<NSConditionLock: 0x1282b6

520> '(null)') unlocked when not locked

2009-03-08 19:22:48.818 java[31539:16703] *** Break on _NSLockError() to debug.

Mar 8, 2009 7:22:48 PM com.jme.renderer.lwjgl.LWJGLRenderer <init>

INFO: LWJGLRenderer created. W:  640H: 480 Version: 2.0.1

2009-03-08 19:22:49.269 java[31539:16703] *** -[NSConditionLock unlock]: lock (<NSConditionLock: 0x1282c1

c70> '(null)') unlocked when not locked

2009-03-08 19:22:49.270 java[31539:16703] *** Break on _NSLockError() to debug.

2009-03-08 19:22:49.373 java[31539:16703] *** -[NSConditionLock unlock]: lock (<NSConditionLock: 0x1282c2

3b0> '(null)') unlocked when not locked

2009-03-08 19:22:49.375 java[31539:16703] *** Break on _NSLockError() to debug.

Mar 8, 2009 7:22:49 PM com.jme.app.BaseSimpleGame initSystem

2

Looks like Josh Slack knows something about this, see



http://blog.renanse.com/2008/07/swt-support-and-mac-pains.html



… delving  -CR

3

Ok, since I am not actually building JME in Eclipse, just building applications on top of it, all I needed to do was remove swt.jar from the build path for the application project.



-CR

4

Actually it appears you need to remove swt.jar AND jme-swt.jar from the build path in Eclipse to fix the problem.



-CR

5

Thanks for putting up your question and solution  :smiley:



i can confirm that removing swt and jme.swt from the build path works for all you mac peeps out there