From mint-bounce@lists.fishpool.fi Sun Dec 28 12:25:41 2008 Subject: Re: [MiNT] an urgent GEM question :-) From: Petr Stehlik To: mint@lists.fishpool.fi In-Reply-To: <1230456363.6300.5.camel@joy> References: <1230022147.7318.6.camel@joy> <20081223172329.6b2125e8@phineus> <1230456363.6300.5.camel@joy> Content-Type: text/plain; charset="ISO-8859-2" Date: Sun, 28 Dec 2008 18:20:07 +0100 Message-Id: <1230484807.6224.9.camel@joy> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pstehlik@sophics.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id mBSHPUxI020477 Petr Stehlik píše v Ne 28. 12. 2008 v 10:26 +0100: > Johan Klockars píše v Ne 28. 12. 2008 v 01:06 +0100: > > The above actually does not mention a hardware cursor, but it is also > > obvious that it is not the normal mouse cursor that v_dspcur() is > > doing anything with. > > Thanks, I think it's clear now. So to answer my original question - for > positioning (our normal) mouse cursor the AES' appl_tplay() is the only > working method - thus the correct one to use. It seems to be working > fine in single TOS and N.AES so we'd just need an implementation of that > for XaAES to allow me to use that in my accessory. > > Question is how to implement it in XaAES. It would be good to know how > the N.AES does that. Wow! I have just got an information that N.AES uses the following two functions in appl_tplay's mouse positioning: vsin_mode and vrq_locator. Well, I would never expect something like that but I admit I am not a VDI expert. The comments under these functions' descriptions in Compendium are most interesting ("don't use or you confuse AES" :) Petr