On Tue, 19 Jun 2001, Brian S. Julin wrote:
> > Stuff to do before release-candidate (IMHO):
> > 
> > 1) Modify Changelog of LibGII/LibGGI, check/update other in-tree docs.
> 
> Still TD

Maybe we should just let this slide for the release-candidate, and make
sure to do it before the final release.

> > 2) Add Grab or Split input function to prevent segfault when closing
> >    visuals whose inputs have been joined.

done.  I added the GGI side just now.  Eric, Steve, note I had updated
the docs before you committed the new files, so changes will need
to be brought over to the new docs.

> > 3) cursor keys in dga seem to be malfunctioning
> > 
> >    Actually, display-dga as a whole seems nonfunctional,

Andy narrowed the cause of this down to DGA's parsing of the 
XF86Config file, but no fix yet.

> > 4) Remove KGIcon to an attic, disable fbdev-mga on MGA1064

Stuff I would like to remove, as soon as we have an attic (I asked
Eman for a tarball of old CVS with RCS files.)

./default/kgi
./display/kgi
./display/suidkgi
./programs/util/monitest/kgitune.c
./programs/util/monitest/kgitune.h
./include/ggi/default/genkgi.h

...plus yanking the KGI code out of fbdev target and adjusting all build 
files, also disabling MGA1064 in the accell list -- though I haven't tried
the G400 hack on it yet, perhaps same problem...

> > 5) svgalib problems:
> >    target doesn't seem do frames
> 
> smoke says this just isn't implemented as far as he can see, and would
> be a chore to implement; we should ensure that mode requests with
> frames > 1 actually fail, rather than pretending to work.

> >    won't vc-switch back to X afterward
> >    doesn't work with ggiteleserver

> Have not figured out why these two happen yet.

Anyone is welcome to tackle this, but once DGA is fixed I wouldn't want
to hold things up further as this could take a while, depending on
how cooperative svgalib is.

> > 6) Running -inroot under 8bpp X stops other apps from running

Fixed and committed.

I think we should fix 3 and 4 and release -- comments?


--
Brian

Reply via email to