From mint-bounce@lists.fishpool.fi  Fri Jan 28 22:22:59 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Date: Fri, 28 Jan 2005 22:24:00 +0100
From: "Arnaud BERCEGEAY" <arnaud.bercegeay@free.fr>
To: mint@fishpool.com
Subject: Re: [MiNT] wind_xget()
References: <200501121959.p43578@b.maus.de>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Message-ID: <opslb0eab88yw5lr@localhost.localdomain>
In-Reply-To: <200501121959.p43578@b.maus.de>
User-Agent: Opera M2(BETA1)/8.00 (Linux, build 913)
Content-Transfer-Encoding: quoted-printable
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: arnaud.bercegeay@free.fr
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=1.1 tagged_above=-50.5 required=3.8 tests=BAYES_00,
 RCVD_IN_SORBS
X-Spam-Level: *

Hello,

> AB> BTW, we can keep this value for WF_FIRSTAREAXYWH (13).
>
> I think no.
>
> AB> Applications should first make sure that AES supports this value (b=
y
> AB> calling appl_getinfo)
>
> The problem at this time (Jun 1995) was to find out is the mode
> WF_OWNER present. This mode is available since AES 3.3, but

So, if such old application runs on a modern AES (with FIRSTAREAXYWH=3D13=
 =20
implemented), and if wind_get(13) returns TRUE, then this old application=
 =20
may believe that WF_OWNER is not supported by this AES. That's not so =20
disastrous.

BTW, this mode (13) should be only called by wind_xget(), and never by =20
wind_get() because this mode (13) expects some data (a clipping area) in =
=20
aes_intin[2..5] (that's the only difference between wind_get and =20
wind_xget: some additional data are put in aes_intin[2..5]).

So i suggest that MyAES and XaAES return 0 if wind_get(13) is invoked wit=
h =20
aes_control[1]!=3D6.

That way, i think that everybody will be happy.

I put hereafter a piece of code to refresh your mind about the subject we=
 =20
discuss here...

> So you can do this to test if an wind_get/set mode is supported:
>
> returnValueOfWindGetSetIsOK =3D wind_get( 0, 13, &ign, &ign, &ign, &ign=
)
> =3D=3D 0;
>
> New wind_get/set returns 0 for an error, and true if everthing is all
> right. Older AES version (before 3.31) returns always true.
>
> int WindGetOwnerID( int windowID )
> {
>   int ownerID, i;
>
>   if (!returnValueOfWindGetSetIsOK)
>       return -1;
>   if (wind_get( windowID, WF_OWNER, &ownerID, &i, &i, &i) =3D=3D 0)
>       return -1;
>   return ownerID;
> }
>

best regards,
Arnaud.