C (83/207)

From:Adrien HEMERY
Date:12 Dec 99 at 10:03:24
Subject:Re: Some questions

From: Adrien HEMERY <iliak_@club-internet.fr>

Hello Duane

> You should also consider a normal Intuition screen. IDCMP doesn't
> really involve that much extra overhead if you're not interested
> in mouse movement events and you can have RTG support if need be.
> The SA_Exclusive tag can be used for taking control of the full
> screen real estate and to prevent screen dragging.

Yes, but i cant get idcmp events only by windows. Screens cant !!

>It isn't nice
> filtering events under these circumstances but I really can't see
> the point in preventing the user from screen cycling (in fact,
> some demo coders go to great lengths to ensure that their display
> hardware takeover code is still capable of allowing screen cycling,
> but you get this for free with system screens).
>
> If you need example event filtering code or display hardware
> takeover code let me know (they're in asm though, this sort
> of stuff usually is).

Ok, what i'll do is to setup a CGFX screen (640x480x8) ans open a
backdrop | borderless window. I'll catch every IDCMP events.

Now i got an other prob. I want to double buffer this window. How can i do
it in CGFX ??? I mean, all docs i have deals with double buffer in planar.
Is it a different way to handle it with a CGFX screen ?

If some1 have some example, i'll be glad to have some...

Regards