On 18 Apr 2000, Marcus Sundberg wrote:
> Stefan Seefeld <[EMAIL PROTECTED]> writes:
>
> > Speaking about video and animation, may I come back to
> > a suggestion I had a couple of weeks back ?
> >
> > I proposed to separate the 'Visual' structure into a
> > 'Drawable' and a part concerned about event handling.
> > The argument is quite in line with Andreas' request to
> > refactor functionality in decompressing and drawing:
> > Drawing and event handling have *nothing* to do with
> > each other.
>
> Sure they do, how else would you know what happens to the visual?
> Expose events and such.
>
> Besides I'm not really sure what you mean by separating out the
> event handling from the visual structure. Of the whole ggi_visual_t
> there is one single pointer related to event handling, isn't that
> separated enough for you?
I don't know what Stefan's reasons are, but mine are simple. If I want to
use GGI's event mechanism (and I mean GGI not GII), I'd like to be able to
select (no output, use stdout for now) and then switch to (have output) at
some point. Basically, I'd like to be able to enable and disable output
to fbdev. I don't have this problem with any other driver....
(if FB gets initialized when X is running my system halts. I need the
event system initialized though before that point. What can I do?)
So my problem's FB/specific whereas his is a little more general.
Actually I'm kind of wondering what he means too?
> A manager for video memory will be implemented in LibGGI soon,
> Andy and I have just talked about that. This will make it simple
> to implement an extension for offscreen images.
PLEASE! :) :) :)
ps: glide has one in their source... it's necessary for handling
texture,double buffer, and so forth...
G'day, eh? :)
- Teunis
