Login  Register

Re: JOGL 2 support for Ardor3D, JMonkeyEngine 3, jzy3d and NiftyGUI

Posted by Sven Gothel on Oct 19, 2011; 9:06am
URL: https://forum.jogamp.org/JOGL-2-support-for-Ardor3D-JMonkeyEngine-3-jzy3d-and-NiftyGUI-tp1706747p3433764.html

On Wednesday, October 19, 2011 10:41:41 AM gouessej [via jogamp] wrote:
>
> Hi
>
> The Ardor3D team seems very busy with the switch to Google Code (and maybe
> GIT). However, I agree with your suggestions. The merge is crucial, it will
> become mandatory when JOGL 2.0 has its first stable release.

We already got 3 of them (rc 1-3), a 4th one is coming up.
So .. IMHO .. the time is now anyways.

To make things easier, I like to add your Ardor3D branch to Jenkins
as a transitional phase. Do you like to participate in this effort ?

> We have to
> speak to them, we have to agree about the evolutions of this renderer (ES
> isolation, multiple screens support, JInput support, etc...).

ES isolation sounds great.

>
> Yesterday, I forgot to speak about a minor problem. One of the bugs I
> reported may annoy Ardor3D users who do not wish to switch to NEWT,
> setAutoSwapBufferMode(false) is still buggy.

Please advise! Do we have a bugzilla bug # ?

>
> I didn't know that ffmpeg could be used to perform screencasts, thanks for
> the tip.

"ffmpeg -pass 1 -f x11grab -r 60 -threads 2 -s 854x480 -sameq -aspect 16:9 -i :0.0 output.avi"

>
> Why can't a NEWT KeyEvent be set to consumed?

I had this discussion with Rami almost a year ago,
where he asked for the same feature.

Instead of allowing an event listener to silent an event
(IMHO somehow weired), we solved it in a cooperate
and pretty generic and flexible way:

http://jogamp.org/deployment/jogamp-next/javadoc/jogl/javadoc/com/jogamp/newt/event/NEWTEvent.html#setAttachment%28java.lang.Object%29
http://jogamp.org/deployment/jogamp-next/javadoc/jogl/javadoc/com/jogamp/newt/Window.html#addKeyListener%28int,%20com.jogamp.newt.event.KeyListener%29

So you are able to be the 1st KeyListener in the queue
and able to attach an Object to the event.
The other listener may respect that object and acts accordingly,
in your case do nothing.

This mechanism is also able to do much more, ie pass results etc.

Hope this mechanism is applicable to your use case as well.

~Sven

>
> -----
> Julien Gouesse