From: Andreas Beck <becka@rz.uni-duesseldorf.de>
  To  : ggi-develop@eskimo.com
  Date: Mon, 28 Jun 1999 17:36:43 +0200

Re: Release request

> I'd like to request that the GGI userspace graphics library please be
> released.  

We are checking some minor issues. Maybe we are a bit too perfectionistic,
but actually where is the problem ?

The Betas are pretty much as good as what others would call a release.

> of GGI last summer and it was working well enough, and now a year later we
> still don't have a stable release.

It's probably a matter of what one calls stable. I think The LibGGI Betas
are as stable as what others would call final release with fixpacks 1-5
applied :-).

>  1) The hwcursor seems to stick on the screen sometimes when I switch to
>     DGA mode.  I just started experiencing that recently, only with GGI
>     programs, but possibly just out of luck.  I tried doing an ugly hack
>     to set the cursor myself, but GGI has no display-dependant code to
>     give me, say, its X Display variable (shouldn't there be?).

No. That's more or less the point of LibGGI. A LibGGI extension is allowed
to know such stuff, to allow for doing such effects, but it is usually not
recommended.

>  2) Timing code has been a total bitch, partly because it appears that
>     GGI uses setitimer using ITIMER_PROF, 

That shouldn't be the case. The setitimer is only used if LibGGI is operated
in SYNC mode. This is discouraged anyway. Use SYNC mode whenever possible.

>     Is there any way of doing frame-rate limiting code portably?

You mean limiting in the sense of timing, not synchronizing to the
CRT-ray ? Use the time argument for ggiEventPoll.

>  3) Could someone maybe write a small tutorial on getting mouse input,
>     especially in the context of DGA games? 

??? Mouse input should work the same no matter what target you have. The
only difference is, that some targets have absolute mouse events, while
others have relative ones.

>  4) Is there no way to do faster blits or let me myself have more
>     control of video memory, especially when we're drawing to a display
>     like DGA that does give reasonably direct access?

DirectBuffer ?

>  5) Any advice on syncing to refreshes?  I've found it basically
>     impossible, but I thought I'd ask anyways.

If the underlying target supports it, you can do so via the ggimisc
extension.

CU, ANdy

-- 
= Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =