next »

[Marvin Fröhlich]

SWT support is now complete .

Well there are still minor problems. But it fully works.

One of the minor problems is, that when the mouse and keyboard are initialized the following lines ore dumped to stdout:

Code:

X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  148
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  148
  Minor opcode:  3
  Resource id:  0x0
Failed to open device

Mouse and Keyboard work anyway. But maybe someone knows, what that is. Google says nothing.

The other "bug" is, that it doesn't seem to be possible to invoke rendering from a separate thread. This will throw the following exception:

Code:

Exception in thread "Thread-3" org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:3374)
at org.eclipse.swt.SWT.error(SWT.java:3297)
at org.eclipse.swt.SWT.error(SWT.java:3268)
at org.eclipse.swt.widgets.Widget.error(Widget.java:434)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:373)
at org.eclipse.swt.opengl.GLCanvas.setCurrent(GLCanvas.java:268)
at org.xith3d.render.jsr231.CanvasPeerSWTImpl.doRender(CanvasPeerSWTImpl.java:304)
at org.xith3d.render.jsr231.CanvasPeerSWTImpl.render(CanvasPeerSWTImpl.java:320)
at org.xith3d.render.jsr231.CanvasPeerImplBase.render(CanvasPeerImplBase.java:1043)
at org.xith3d.render.Renderer.renderOnceInternal(Renderer.java:591)
at org.xith3d.render.Renderer.renderOnce(Renderer.java:617)
at org.xith3d.render.Renderer.renderOnce(Renderer.java:661)
at org.xith3d.render.Renderer.renderOnce(Renderer.java:676)
at org.xith3d.scenegraph.VirtualUniverse.renderOnce(VirtualUniverse.java:161)
at org.xith3d.scenegraph.View.renderOnce(View.java:686)
at org.xith3d.render.base.Xith3DEnvironment.render(Xith3DEnvironment.java:387)
at org.xith3d.render.loop.RenderLoop.invokeRendering(RenderLoop.java:813)
at org.xith3d.render.loop.RenderLoop.loopIteration(RenderLoop.java:834)
at org.xith3d.render.loop.ExtRenderLoop.loopIteration(ExtRenderLoop.java:349)
at org.xith3d.test.benchmark.Q3FlightBenchmark.loopIteration(Q3FlightBenchmark.java:207)
at org.xith3d.render.loop.RenderLoop.nextIteration(RenderLoop.java:1010)
at org.xith3d.render.loop.RenderLoop.run(RenderLoop.java:1074)
at java.lang.Thread.run(Thread.java:619)

Any idea?

I cannot imagine, that is not possible at all. But if you want to use SWT rendering, start the RenderLoop with

Code:

begin( RunMode.RUN_IN_SAME_THREAD );

And everything is fine.

Enjoy .

Marvin

[starscream]

Hi,

maybe this helps:

http://ubuntuforums.org/showthread.php?p=1264009

Seems to be a x-org-conf-problem...

[Marvin Fröhlich]

Hi,

maybe this helps:

http://ubuntuforums.org/showthread.php?p=1264009

Seems to be a x-org-conf-problem...

Thanks for the link. Looking forward to solve the problem with your tip.

Marvin

['n ddrylliog]

Well, don't know if to say thanks since we worked on it together but anyways, great ! 

[horati]

Last night, I thought I saw a tutorial for getting an SWT app up and running.  I've been poking through the code and boards and cannot seem to find it today.  All I find are some rendering/canvas peer classes.  Can you point me to such a tutorial?

Has anybody run X3D SWT as an Eclipse plug-in yet?  I plan to do so and will either pioneer it (with help from the sith lords needed) or follow in somebody's footsteps.

[Marvin Fröhlich]

Last night, I thought I saw a tutorial for getting an SWT app up and running.  I've been poking through the code and boards and cannot seem to find it today.  All I find are some rendering/canvas peer classes.  Can you point me to such a tutorial?

The only thing, you need to do is to use OpenGLLayer.JOGL_SWT as a Canvas3DFactory parameter (or Canvas3DWrapper, if you're not using the trunk). And you need to pass a RunMode.RUN_IN_SAME_THREAD parameter to the begin mode of the RenderLoop. Then it should work without any further modification to other projects.

Has anybody run X3D SWT as an Eclipse plug-in yet?  I plan to do so and will either pioneer it (with help from the sith lords needed) or follow in somebody's footsteps.

No. I don't think, anybody has done this. Good luck.

Sith Lords will always help .

Marvin

['n ddrylliog]

"Good Luke", horati 

Marvin, remind me, there wasn't anyway to avoid this nasty "Run in the same thread" thing ?

[Marvin Fröhlich]

"Good Luke", horati 

Marvin, remind me, there wasn't anyway to avoid this nasty "Run in the same thread" thing ?

Well, not yet. When force tells me a better way, I will let you know.

Marvin

[horati]

In order to add it as a plug-in within Eclipse, you have to attach it to a Composite instance created by the framework in a call within one of their threads.  If I understand the Xith3D mechanism correctly, it requires that I give it control and use synchronous mode.  This isn't going to work.

I greatly prefer X3D but didn't realize it supported SWT when I started my project.  So I was able to get Aviatrix3D running within an Eclipse view without too many problems without using a blocking thread.  Going that route, my only problems were getting A3D to do what I wanted because it has far fewer features of a gaming nature.

If anyone is interested, here is the code necessary within Eclipse to get an A3D scene up and running as well as the source to the A3D SWT Canvas which is also based on org.eclipse.swt.  I'm not sure what it does differently to make Threads work but I'll be happy to help investigate if you give me some direction where to go/what you need to see.

[horati]

One more file... there was a 4 file limit.

[horati]

I'm adapting some of the tests to run with SWT.  I just adapted the HUD3DTest.java which most definitely does not work with SWT due to the threading bug In an effort to reduce the amount of debugging, I reduced the number of controls and listeners and such that were in HUD3DTest.java.  Here are the 2 files I produced to create this test.

Here is what I experience:

• The application comes up with only an exception that it cannot find the GTK theme so it is using the fall back theme
• The HUD renders
• The scene renders
• The scene animates
• Whenever I click a button, instead of the listeners firing correctly, the following exception prints twice (exactly the same way both times):

  Exception in thread "AWT-AppKit" org.eclipse.swt.SWTException: Invalid thread access
          at org.eclipse.swt.SWT.error(SWT.java:3374)
          at org.eclipse.swt.SWT.error(SWT.java:3297)
          at org.eclipse.swt.SWT.error(SWT.java:3268)
          at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
          at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
          at org.eclipse.swt.widgets.Control.isEnabled(Control.java:1476)
          at org.eclipse.swt.widgets.Display.mouseProc(Display.java:2764)
  

• Whenever the program loses focus, the following exception prints once:

  Exception in thread "AWT-AppKit" org.eclipse.swt.SWTException: Invalid thread access
          at org.eclipse.swt.SWT.error(SWT.java:3374)
          at org.eclipse.swt.SWT.error(SWT.java:3297)
          at org.eclipse.swt.SWT.error(SWT.java:3268)
          at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
          at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
          at org.eclipse.swt.widgets.Control.isEnabled(Control.java:1476)
          at org.eclipse.swt.widgets.Display.getFocusControl(Display.java:1507)
          at org.eclipse.swt.widgets.Decorations.saveFocus(Decorations.java:393)
          at org.eclipse.swt.widgets.Shell.kEventWindowDeactivated(Shell.java:967)
          at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2040)
          at org.eclipse.swt.widgets.Display.windowProc(Display.java:4032)
  

• Whenever the program gains focus, the following exception prints once (very similar but a little different):

  Exception in thread "AWT-AppKit" org.eclipse.swt.SWTException: Invalid thread access
          at org.eclipse.swt.SWT.error(SWT.java:3374)
          at org.eclipse.swt.SWT.error(SWT.java:3297)
          at org.eclipse.swt.SWT.error(SWT.java:3268)
          at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
          at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
          at org.eclipse.swt.widgets.Control.forceFocus(Control.java:782)
          at org.eclipse.swt.widgets.Decorations.restoreFocus(Decorations.java:388)
          at org.eclipse.swt.widgets.Shell.kEventWindowActivated(Shell.java:909)
          at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2036)
          at org.eclipse.swt.widgets.Display.windowProc(Display.java:4032)
  

• The ESC key listener works fine

Please let me know if I can create more test cases.  Obviously, I'll take my own shot at fixing it; however, based on my current X3D knowledge, I will be more use to everyone if I track down tests, documentation, and research.

Also of note:

• When I launch from the Eclipse launcher, the program pops up, does not display the scene, and disappears without terminating.  Visual display, including animation, is fine if I run from the command line with the same java.library.path and classpath.  Since I haven't been here long enough to prove my competence, I'll state how I got the paths: I ran the program from the Eclipse launcher and copy/pasted the relevant output from System.getProperties().store( System.out ).  I attached a copy of my command line execution script.
• There do exist some JOGL problems on Mac OS X.  Apple has been notified and is working on them.  It would be good if someone run this test case on a non-OS X environment to verify
• I won't be around to help much longer today to help because I have a date in a little while.  I'll definitely be back at it tonight or tomorrow morning (US Eastern Time).

Edit: I SVN updated and get the same result.  Only change to the previously posted code is

Code:

        Tuple2f borderSize = new Point2f();
        this.getSizeOfPixels( 6, 6, borderSize );

[Marvin Fröhlich]

I will check your files later. But the HUD3DTest runs out-of-the-box from SVN with SWT. It extends the MD2LoaderTest, which is set up to run the RenderLoop in the same thread (MD2LoaderTest, line 256), which I have done espeacially to get it working with SWT.

Isn't it running on your machine?

Marvin

[horati]

Nope.  Out of the box, it runs fine using JOGL_AWT but JOGL_SWT has no mouse movement at all and I get these exceptions when the program gains/loses focus or I hit the ESC key:

org.eclipse.swt.SWTException: Invalid thread access
        at org.eclipse.swt.SWT.error(SWT.java:3374)
        at org.eclipse.swt.SWT.error(SWT.java:3297)
        at org.eclipse.swt.SWT.error(SWT.java:3268)
        at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
        at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
        at org.eclipse.swt.widgets.Control.isEnabled(Control.java:1476)
        at org.eclipse.swt.widgets.Display.getFocusControl(Display.java:1507)
        at org.eclipse.swt.widgets.Decorations.saveFocus(Decorations.java:393)
        at org.eclipse.swt.widgets.Shell.kEventWindowDeactivated(Shell.java:967)
        at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2040)
        at org.eclipse.swt.widgets.Display.windowProc(Display.java:4032)
org.eclipse.swt.SWTException: Invalid thread access
        at org.eclipse.swt.SWT.error(SWT.java:3374)
        at org.eclipse.swt.SWT.error(SWT.java:3297)
        at org.eclipse.swt.SWT.error(SWT.java:3268)
        at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
        at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
        at org.eclipse.swt.widgets.Control.forceFocus(Control.java:782)
        at org.eclipse.swt.widgets.Decorations.restoreFocus(Decorations.java:388)
        at org.eclipse.swt.widgets.Shell.kEventWindowActivated(Shell.java:909)
        at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2036)
        at org.eclipse.swt.widgets.Display.windowProc(Display.java:4032)
org.eclipse.swt.SWTException: Invalid thread access
        at org.eclipse.swt.SWT.error(SWT.java:3374)
        at org.eclipse.swt.SWT.error(SWT.java:3297)
        at org.eclipse.swt.SWT.error(SWT.java:3268)
        at org.eclipse.swt.widgets.Widget.error(Widget.java:653)
        at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
        at org.eclipse.swt.widgets.Control.getShell(Control.java:1123)
        at org.eclipse.swt.widgets.Control.translateTraversal(Control.java:3265)
        at org.eclipse.swt.widgets.Control.kEventTextInputUnicodeForKeyEvent(Control.java:1800)
        at org.eclipse.swt.widgets.Widget.textInputProc(Widget.java:2000)
        at org.eclipse.swt.widgets.Display.textInputProc(Display.java:3838)

[Marvin Fröhlich]

Hmmm... It runs on my system. Which Operation System do you use? I'm running Linux and Java 1.6. And I've successfully tested it on Windows XP and Java 1.5.

Unfortuantely I cannot download any of the attached files. Could you please send them via mail (check your PM)?

Marvin

[horati]

I missed this request for the files via e-mail.  I run Mac OS X 10.4.8.

I am happy to announce that I have fixed the SWT threading issue in my local environment.  I need to perform more a lot more testing as well as gain developer SVN access before I commit the changes.  There was an issue with illegal creation of SWT Displays that I fixed as well.

Edit: I'm going to take the rest of the day off.  I'm exhausted after putting in 110 hours in the last 8 days.  Hopefully, somebody can grant me SVN access overnight so I can test and commit the fixes tomorrow.