On Thu, 21 Jun 2001, Brian S. Julin wrote:
> > > 3) cursor keys in dga seem to be malfunctioning
> > >
> > > Actually, display-dga as a whole seems nonfunctional,
Updating the internal XF86Vmode implementation did the trick for me.
Note: this will make the xf86dga target build fail on a system
with older XF86VMode -- but binaries generated on a system with
new XF86VMode should still work on a server with older XF86VMode
implementations. I tested on a 3.3.6 server (XF86VMode v0.8)
where I built with 4.0.3 libraries, and on a 4.0.3 server
(XF86VMode v2.0). This change also got rid of a segfault I
was experiencing on the 4.0.3 server.
I never did see any trouble with the cursor keys.
Andy, how's the new code treat your system?
We can slate true DGA2.0 support for LibGGI2.1, what we have
now will work for most everyone (sound of wood being knocked on.)
> > > 5) svgalib problems:
> > > target doesn't seem do frames
CVS now contains some untested code for frames support
John will pick this up on Monday.
> > > won't vc-switch back to X afterward
I can now test this problem. Looking into this now.
> > > doesn't work with ggiteleserver
> > Have not figured out why
Are we going to wait for DirectX updates before announcing
the release candidate? BTW, can anyone offer me some pointers
to instructions on how I would go about building/testing
cygwin and the DirectX target? I do have a Win98 box handy these days.
Also, it was mentioned that cygwin was needed because of
ggiSelect -- 1) what are the pros/cons of cygwin being needed?
and 2) Is it possible to build without cygwin and just omit
the ggiSelect call from the API? It is documented that it may
not be available on some systems.
--
Brian
