LWJGL
October 01, 2014, 07:14:44 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: LWJGL is now using GitHub
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: LWJGL 1.1 Released  (Read 16107 times)
Matzon
Administrator
Demigod
*****
Posts: 2242



« on: April 30, 2007, 14:12:50 »

LWJGL 1.1 released

Download
Release notes

As always, consider donating if you use LWJGL.
Logged

ndhb
Regular nerd
**
Posts: 70


« Reply #1 on: April 30, 2007, 22:13:32 »

Well done!

Awesome work (VBO performance seems much improved on my platform).

- Nicolai de Haan Brøgger
Logged
princec
Nerdus Imperius
*****
Posts: 1878



WWW
« Reply #2 on: May 01, 2007, 04:27:58 »

Criminy, you guys have been busy! What brought that flurry of development on?

Cas Smiley
Logged

Matzon
Administrator
Demigod
*****
Posts: 2242



« Reply #3 on: May 01, 2007, 06:48:25 »

well, I've been delaying oal 1.1 for a while, guess I caved in.
as for elias, I just think he gets bored sometimes...
Logged

Fool Running
Nerdus Imperius
*****
Posts: 828


« Reply #4 on: May 02, 2007, 18:11:28 »

Sweet, a new release Grin

Keep up the good work Cool
Logged

Programmers will, one day, rule the world... and the world won't notice until its too late.Just testing the marquee option Grin
numberR
Talks Too Much
***
Posts: 101


« Reply #5 on: May 02, 2007, 21:17:00 »

Great!
Logged
bobjob
Prolific Timewaster
****
Posts: 335


LWJGL: WOW SO GOOD


« Reply #6 on: May 03, 2007, 09:21:00 »

awsome, thanx guys keep up the good work Cheesy
Logged

LWJGL Benchmark online test:
http://have2chat.net/benchmark/
http://have2chat.net/benchmark/fullpage.html (run full OpenGL webpage)
mot
Regular nerd
**
Posts: 57


WWW
« Reply #7 on: May 03, 2007, 15:03:15 »

Great, thanks to all LWJGL developers. I just sent you a small donation, have a beer or something.

[EDIT] Is it just on my machine or is the Windows mouse acceleration being taken into account when it's in "grabbed" mode? I saw the changes in the ChangeLog but I'm not sure if this is intended. Until now I was doing my own mouse acceleration to compensate because in the "grabbed" mode the cursor was much slower.
Logged

Tom Andrle - Catnap Games - http://www.catnapgames.com
elias
Nerdus Imperius
*****
Posts: 899



WWW
« Reply #8 on: May 04, 2007, 13:25:42 »

Is it just on my machine or is the Windows mouse acceleration being taken into account when it's in "grabbed" mode? I saw the changes in the ChangeLog but I'm not sure if this is intended. Until now I was doing my own mouse acceleration to compensate because in the "grabbed" mode the cursor was much slower.

This is expected, since we've gone from using directinput to using windows messages for input, which takes configuration parameters like mouse acceleration into account. The downside is that this is a change from previous LWJGL versions, the upside is that the mouse should now be consistent on all platforms (since acceleration is applied on mac and linux LWJGL input).

@princec: The directinput->windows messages work was needed because multiple mice through JInput don't work when DirectInput is active (this is an inherent flaw in the windows implementation of Raw Input and DirectInput). The non-direct buffer support was inspired because I realized they could be supported with very little (and constant) code size overhead and no performance overhead.

 - elias
Logged

stramit
Newbie
*
Posts: 4


« Reply #9 on: May 04, 2007, 15:54:44 »

Quote
Make the rest of LWJGL thread safe. No attempt have been done to make the locking minimal. Instead, one global lock is shared by Display, Mouse, Keyboard and Cursor. The lock surrounds all public methods.
Quote

What exactly do you mean by this? It seems that you have just made it so that LWJGL can be accessed by multiple threads, but isn't that slightly odd seeing as only one thread can have the GLContext at a time? Or do you mean that LWJGL now holds the context and all calls (no matter which thread they are from) end up using the correct context?

To me it sounds like the first, but there doesn't really seem much point to it aside from helping the integrity of the library. I would love to know the reasoning.
Logged
elias
Nerdus Imperius
*****
Posts: 899



WWW
« Reply #10 on: May 05, 2007, 01:13:56 »

You're absolutely right, both OpenGL and OpenAL are thread safe by specification. However, there's still a few bits of LWJGL specific code (Display, Mouse, Keyboard, Cursor) that is not a direct binding to an underlying API. They carry internal LWJGL state and have to be synchronized, which is what the changelog entry refers to.

 - elias
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
SMFAds for Free Forums
Valid XHTML 1.0! Valid CSS!