On Wed, Mar 31, 2010 at 12:10 PM, Eric Iverson <[email protected]> wrote: > The j602 opengl does not depend on any special isigraph/canvas options (as > did previous versions). It moves pixels from the opengl data to the isigraph > directly by copying the pixels from the opegl internal buffer to the > isigraph buffer. As Raul stated, there is no isigraph mechanism that is > peculiar or special for opengl.
If pointing an opengl maintainer at J's opengl demos is "too hard" for the maintainer, then perhaps we can ask for some support in a different fashion. In principle, the developer could release a "logging" version of a library. In other words insted of using libgl1-mesa-glx's /usr/lib/libGL.so.1.2, you would temporarily install libgl1-mesa-glx-dbg-log which would provide a version of /usr/lib/libGL.so.1.2 that logged to file every call to every one of its entry points. This version would, of course, be slower than the regular version, but it would also allow you to create a log and include it with a bug report which would allow the developer to replay the sequence of events you used to trigger the bug, without getting into the hassle of learning a new computing environment. If they are going to release buggy libraries, they are going to need some kind of tool which lets them inspect errors which occur in the field. And while I can think of other approaches, this one has is relatively easy to implement and deploy. FYI, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
