LWJGL alpha 0.8 released

OpenGL Development
#1

New stuff:

  1. Mac port
  2. Various small API changes - most notably the native cursor starting point is now the middle of the window, not the lower, right corner.
  3. Lot of bug fixes and added OpenGL extensions.
  • elias
#2

looks like it’s stabilizing ? 8)

#3

Playing with 0.8 now. What exactly is contained in the HashSet when calling GLCaps.determineAvailableExtensions(HashSet)?

How can I make use of this HashSet?

#4

You can’t. We forgot to make the determine… call non-public, as it is now automatically called after a successful Window.create(). It’s been fixed now.

  • elias
#5

Sorry to ask this but I can’t seem to find a working example of lwjgl 0.8 alpha. I got some tuts from NEHE but none of them compile.

Could anyone post me a link that has up to date tuts for lwjgl.

Thanks.

#6

Download the nehe ports from lwjgl site, if you haven’t already. You have to change a couple things, for example:


//sync to monitor
    GLCaps.determineAvailableExtensions();
    if(GLCaps.WGL_EXT_swap_control) {
      GL.wglSwapIntervalEXT(1);
    }

just comment that block of code out, it’s unneeded. It should be replaced by a

Window.setVSyncEnabled(true);

(I placed it right below the Window.create(…) line, but I found it to be “unnecessary” for the demos. Maybe in another context I’ll find it important… :slight_smile:
You may also have to comment out the package line on line 1, but you may not. I didn’t import the filesystems “correctly” in eclipse. :stuck_out_tongue:

I would “submit” my fixes, but I lack CVS access nor am I sure that my “fixes” are actually the correct way of doing things. :slight_smile:

#7

Actually, I just dropped that Window.setVSyncEnabled(true); line in the spot that I commented out and it seems to be working just fine. I think I tried it before and got compile errors, due to something else…

#8

I see you’ve also added mouse button buffering :slight_smile:

BTW. I’ve noticed that when disabeling the native cursor by calling setNativeCursor(null), the change don’t take effect until I call Mouse.poll(). Is this is a bug, or by design? I’m using windows.

#9

poll() doesn’t do anything special to the mouse cursor - I’m suspecting the mouse image is only updated by Windows when the mouse actually moves (or is polled through DirectInput).

  • elias
#10

Well the image of the custom cursor disapears, but the operating system still has access to it. It is visible if I move the cursor outside the window. And although the cursor is not visible inside the window, the minimize, maximaze, close, move etc still works.

I was expecting that calling “Mouse.setNativeCursor(null);” would give me exclusive control of the mouse. But this happens instead when I call Mouse.poll().

This is only an issue in windowed mode.

#11

Oooh, now I get it :slight_smile: I think I know what is causing that. The fix has been checked in.

  • elias