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.
John
On Thu, Feb 01, 2001 at 03:54:36AM -0500, Lee Brown wrote:
> Like I said, I've been working on cursors.
>
> Heres the api. In particular, I wonder if one thing I did was acceptable. I
> allow multiple cusors to be loaded into the visual. The user selects which one
> to show with ggiSetCursor. Is it bad that I require that the cursor handle
> only be used in conjunction with the visual that created it. If you create a
> cursor handle "c" with visual "v", then you had better call ggiSetCursor(v, c);
>
> This I wonder.
>
> Lee
> _________________________________________________________
>
> typedef guint ggi_cursor_t;
>
> typedef struct {
> guint16 bpp;
> guint8 width;
> guint8 height;
>
> ggi_color* palette;
>
> void* bits;
>
> guint16 hot_x, hot_y;
> } ggi_cursor;
>
> GList* ggiListCursors(ggi_visual_t vis);
>
> ggi_cursor_t ggiLoadCursor(ggi_visual_t vis, ggi_cursor* cursor);
> int ggiUnloadCursor(ggi_visual_t vis, ggi_cursor_t cursor);
> int ggiSetCursor(ggi_visual_t vis, ggi_cursor_t cursor);
> ggi_cursor_t ggiGetCursor(ggi_visual_t vis);
>
> int ggiShowCursor(ggi_visual_t vis);
> int ggiHideCursor(ggi_visual_t vis);
> int ggiMoveCursor(ggi_visual_t vis, gint x, gint y);
> gboolean ggiIsCursorShown(ggi_visual_t vis);
>
>
>
>
> --
> Lee Brown Jr.
> [EMAIL PROTECTED]
>
