1. Yes, those things are done in the lab prepare, but they should also be done clearly in the first step or so.

2. glpaintx - you have mentioned this before and only now does a little light go off. glpaintx hasn't changed. It marks the control invalid and that will eventually get a paint message to the host. What has changed it that now the way isigraph works now with a memory buffer it simply says 'got a buffer of the right size and blts it over'. This isn't right, but I'm going to have to think it through a bit.

The way it works now you should: first call the paint handler to do a new drawing to the buffer then call glpaintx so the buffer will be blted when the system next goes idle and processes paint messages.

----- Original Message ----- From: "Miller, Raul D" <[EMAIL PROTECTED]>
To: "Beta forum" <[email protected]>
Sent: Tuesday, April 11, 2006 1:55 PM
Subject: RE: [Jbeta] 601 k beta available for windows


Eric Iverson wrote:
http://www.jsoftware.com/download/j601kbeta_win.exe
The opengl intro lab has been improved and cleaned up.

You are probably already aware of these issues, but to avoid
them falling through the cracks:

[1] opengl intro lab should explicitly mention
  require 'jzopengl'

You know that's needed, and I know that's needed, but someone
new to the environment would not know that that's needed.

[2] glpaintx does not trigger the paint event handler, if
this is intentional, perhaps the documentation for glpaintx
should mention this issue.

Thanks,

--
Raul

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to