"Brian S. Julin" wrote:
>
> Update on the TODO/bugs list.
>
> > 1) Make all targets fill out mode.size when they can.
>
> Committed for most important targets. Still some testing to do.
> (Stefan, have you tried this out yet? If you have time, please
> try display tile/multi/sub to see if they work as well.)
I will implement the checkMode for the ipc target soon (monday
probably).
> Berlin folks would also like to negotiate using the .size member,
> which will simply involve making the various checkmodes behave as they
> should and can be done on an incremental basis.
right, but that's not urgent. That's what we want in the long run.
> 7) Ad Grab or Split input function to prevent segfault when closing
> visuals whose inputs have been joined.
>
> Proposed giiSplitInputs posted to ml, ggiSplitInputs still todo.
there is something in the API which I find extremely unpleasant.
cube3d.c line 109 illustrates my point:
it appears giiJoinInputs is used (with a NULL argument) to return
the ggi_input_t. That's very misleading. I think the least to do
is to add am accessor function, something like 'giiGetInput(ggi_visual_t)'.
That seems trivial to add, but makes the API much more meaningful.
(Of course, ggiJoinInputs can then use this new function, instead of
the other way around).
> > 4) crusty kgicon drivers fail compile (see sf bugs)
>
> Christoph asked whether to create an attic CVS module, or to
> just create an attic tarball. What do folks think?
I don't quite understand why kgicon is part of this project at all.
Didn't Steffen set up a project on sourceforge a long time ago just
for kgicon ?
> > 14) On matroxfb, perhaps all fbdev, when vc is switched away/back
> > displayed frame is always frame 0.
>
> I have an idea as to why this may be, but have not attempted a fix yet.
I use matroxfb with my G450, and I have observed some problems. But since
I neither had time to investigate them, nor am I sure that this is a
GGI issue, I didn't do anything. The problem is/was that text was not
displayed in GGI applications. This however seems to vary depending
on what graphics mode I boot in.
Regards,
Stefan
