From owner-mint@fishpool.com Mon May 26 17:10:33 2003 Date: Mon, 26 May 2003 15:05:32 +0200 (CEST) From: Odd Skancke To: Subject: Re: [MiNT] XaAES In-Reply-To: <20030526164710.A28749@pc272.hrzpub.tu-darmstadt.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: On Mon, 26 May 2003, Thomas Binder wrote: > Hi! > > On Mon, May 26, 2003 at 12:07:32PM +0200, Odd Skancke wrote: > > I seem to be a bit confused as to how N.AES handles clicks on > > the rootwindow (desktop). Under N.AES, single left-clicks on > > empty desktop areas brings Thing ontop. Right-clicks opens up > > Thing's popup. > > > > Seeing this, I made xaaes pass all clicks to Thing's event > > handler. However, left-clicks now did not do anything at all. I > > thought Thing topped itself. Right-clicks behaved just like > > under N.AES. > > Well, Thing _does_ handle this situation itself. But it uses OS > specific calls to top itself, there's a correspondig call in > N.AES. I can't currently recall neither its name nor whether it is > detectable via appl_getinfo(). If you want, I'll look it up in the > code. Aha! If you could look that up in the original code, I'd be very pleased, thanks ;-) I'd like to get XaAES as compatible with N.AES as possible, before going further. > > (The main problem for an application to top itself is to activate > the menu bar, as there's no real standard AES call for that.) Yes, I see the problem. -- Regards, Odd Skancke - ozk.atari.org - http://assemsoft.atari.org