On Thu, 01 Feb 2001, John McCutchan wrote:
> On Thu, Feb 01, 2001 at 07:49:20AM -0500, Lee Brown wrote:
> > On Thu, 01 Feb 2001, John McCutchan wrote:
> > > These seems like overkill to me, Just let the application handle multiple
> > > cursors. I don't think this fits with the rest of the ggi architecture.
> >
> >
> > Right now, how does an application use a hardware cursor?
>
> It doesn't. The application should provide ggi with a cursor and the
> application can dicide to show or hide it. Based on the target ggi
> would use a hardware or a software cursor. My point was that when the
> application wants to change cursors it should give ggi a new cursor
> ggi shouldn't have a list of cursors that could be used on the visual.
> the application should, and it should change it as needed.
OK. I see where you are misled. My bad. the ListCursors is a means of
letting the application know what type of cursors are available to be used
IT DOESN"T PROVIDE CURSORS. It just states what sizes and depths are
available for input. This is similar to getting the available point sizes in
OpenGL.
Good point.
Lee
>
> John
--
Lee Brown Jr.
[EMAIL PROTECTED]
