From mint-bounce@lists.fishpool.fi  Sun Jul 25 11:09:02 2010
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:from:content-type
         :content-transfer-encoding:subject:date:message-id:to:mime-version
         :x-mailer;
        bh=erxJHo0rCYsBtgo4rAxMpwacnAThHgb+9y+JHeI74cM=;
        b=lQXp0GAMwlz7mwrNLUl2m2+5Nz4BHR+qMxTbbavb2JMhUXPHUcIno96hItMp9dJuqE
         RoRMLyzwW4SrhQUOBpspzYtIjfU5GByaQZX32XcawdeuSMPFGA/7l2f7Zxa+qgrvBtAD
         trTzbDH+ftt22BL6P+/4UzwpYG7oVkTJZp8TA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:content-type:content-transfer-encoding:subject:date:message-id
         :to:mime-version:x-mailer;
        b=SORfsoGUFWwqPJ11TNY8TmHWzk8t91mG7IuIi+/aUxZx+odJbbSGZv4t4y9+N5nE9P
         YFSqbpLYs0mQnSpaHDKD8oajL+KgUJwGIoPmgiaiss8H+ezMY2poTHMFeHraVmzrXXPf
         HA7HTWuXjEq24MrxwADIVk58V9Shj2j4hBJ4M=
From: Peter Persson <pep.fishmoose@gmail.com>
Content-Type: text/plain; charset=us-ascii
Subject: [MiNT] The Thing vs. XaAES issue.
Date: Sun, 25 Jul 2010 17:04:16 +0200
Message-Id: <23937111-F30C-49F5-B7C5-0D87281F9631@gmail.com>
To: MiNT Mailingliste <mint@fishpool.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: pep.fishmoose@gmail.com
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>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o6PF91at003321

Hi,

I've posted about this before, but I'm somehow not really sure what happened with this. Thing and XaAES does not quite get along nowadays (1-17). There is a window focus problem.

Now, Thing is one of only three desktops which conforms to "modern" specifications. No matter if the problem is due to a mishap in Thing or if it's a bug in XaAES, the application in question is significant to the platform. In other words, it must work. If not, a workaround is required. Don't get me wrong - I bloody hate workarounds, and bugs should be fixed at the source, but in some sence the AES has to offer some degree of bug-to-bug compatibility.

Thing works well with 1-16. So what exactly happened, and how can it be fixed?

I'll be downgrading to 1-16 again very soon, because this kind of issue effectively prevents me from using my machine. That's bad.

-- PeP