Re: [MiNT] MiNT +problem with background in Teradesk

[Paul Wratt <paul.wratt@gmail.com>]

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) ?

Also your explanation is contrary to how XaAES renders the textures..


>> they showed it was possible for an area of the window to allow the
>> underneath to be seen, which proves it is possible. "how" is a
>> different matter entirely, but some examination will shed light on it.
>
> I explained this to you about a year ago. It won't work unless you change
> the way the AES and VDI works. The problem is that there is nothing beneath
> a window - if a window (including the desktop) is (partially) covered, the
> owning app is never told to redraw the work area so there is nothing to see
> through the window that covers it. It's that simple. The best you can do is
> to see the underlying window frames through the top window frames.
>
That in itself is a starting point. When I find an app with buggy
window redraw's I post about it.

> Jo Even
>

Paul