On 19 August 2010 15:32, Paul Wratt
<paul.wratt@gmail.com> wrote:
On Thu, Aug 19, 2010 at 8:00 PM, Jo Even Skarstein <
joska@online.no> wrote:
> --------------------------------------------------
> From: "Paul Wratt" <
paul.wratt@gmail.com>
> Sent: Thursday, August 19, 2010 10:08 AM
> To: "mint" <
mint@lists.fishpool.fi>
> Subject: Re: [MiNT] MiNT +problem with background in Teradesk
>>
>> by starting with providing a window region that already has a texture
>> in it (before drawing begins). Then looking at how vdi/aes draws
>> objects, and (if code is available) how others are doing textures
>> currently (XaAES)
>
> You need to study how the AES works. Because what you describe won't work.
> The reason is very simple: The AES doesn't know anything about what happens
> inside a window's work area, and the VDI doesn't know anything about
> windows. So basically there is no way the AES can know what apps are doing
> inside the window's work area.
>
So how does AES 4.0 supply 3D work and a modified background color
(normally white on single TOS) ?
You are confusing rendering of RSC objects with drawing actual window contents.
You need to learn how the windowed approach of GEM works before trying to do any AES development, from what I can tell.
Having the AES draw textures (or anything else for that matter) *inside* a GEM windows work area is about as legal as painting the windscreen of your car solid black.
/J