next »

[Marvin Fröhlich]

I have created a new HIAL version. It is also online (1.6.5) at http://input.jtank.net/. The new versions has some additional KeyCodes, but has also lost two of them. The VK_SHIFT and VK_CONTROL have been removed and instead there are VK_LEFT_SHIFT, VK_RIGHT_SHIFT, VK_LEFT_CONTROL and VK_RIGHT_CONTROL. Some key codes did not work for AWT and some not for LWJGL. This is fixed now.

Marvin

[Marvin Fröhlich]

And again a new HIAL release (1.6.6). AWTMouse and AWTKeyboard are now synchronized with the update() method. This means, AWT input is now synchronized with the rendering thread (just as LWJGL is per se).

Now nothing needs to be specially synchronized with the rendering thread when it is triggered by an input event (no matter which OpenGLLayer is used).

The AWT synchronization can be switched off by invoking

Code:

AWTMouse.setSynchronized( false );
AWTKeyboard.setSynchronized( false );

It is done by queueing the AWT input events through abstract HIAL input events. You may have noticed, that the HIAL input listener method signatures have become quite big. It would be very easy now to make the listeners work with these input event classes. Then the onMouseButtonPressed event for example would look like this:

Code:

// currently
public void onMouseButtonPressed(MouseDevice mouse, int button, int x, int y, long when, long lastWhen)
// afterwards
public void onMouseButtonPressed(MousePressedEvent e)

I think, this is more convenient, now where we have so many worthful event properties. What do you think?

Marvin

[EDIT by Amos Wenger : monday, 25 june 2007 : bbtag error]

['n ddrylliog]

It is done by queueing the AWT input events through abstract HIAL input events. You may have noticed, that the HIAL input listener method signatures have become quite big. It would be very easy now to make the listeners work with these input event classes. Then the onMouseButtonPressed event for example would look like this:

Code:

// currently
public void onMouseButtonPressed(MouseDevice mouse, int button, int x, int y, long when, long lastWhen)
// afterwards
public void onMouseButtonPressed(MousePressedEvent e)

I think, this is more convenient, now where we have so many worthful event properties. What do you think?

Definitely for it Don't forget to use pools to reduce GC.

[Marvin Fröhlich]

Don't forget to use pools to reduce GC.

Of course I do this already .

[Marvin Fröhlich]

The change in HIAL is done. Now all the HIAL's event methods use event classes publicly.

Marvin

[William Denniss]

Nice changes

Cheers,
Will

[Marvin Fröhlich]

The latest HIAL version (the one currently used in Xith3D) is now on SVN.

Marvin