From owner-mint@fishpool.com Thu Apr 24 15:41:38 2003 Date: Thu, 24 Apr 2003 07:42:57 +0200 From: Johan Klockars To: mint@fishpool.com Subject: Re: [MiNT] [?] appl_tplay() and appl_trecord() Message-ID: <20030424074256.A11728@verin.klockars.net> References: <5.0.2.1.2.20030418083916.00ac4638@pop.utbm.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i 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: johan@klockars.net Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: > > For appl_tplay() appl_trecord() in last Henck archive doesn't support this > > function at all, like most other AES except TOS an Magic. (not implement in > > OAESIS, XAAES, not work correctly or crash on NAES (crash), GENEVA(timing > > error)) > > As some applications use appl_tplay for setting the mouse position, it I do that myself in MGIF, but... > would be very usefull to have at elast appl_tplay available in XAAES. > > PS: Is there another "legal" method for setting the mouse position? ...there is no legal way for the AES to set the mouse position, since the VDI does not provide that functionality. Obviously, the original AES knew enough about the internals of the original VDI to make this work, anyway. Whatever that knowledge was, it will most likely stop working with fVDI in the not too distant future (fVDI still relies on the original VDI for mouse and keyboard handling). So, XaAES can currently not legally move the mouse about, and thus can not (legally) implement that part of appl_tplay. I'll probably add a new VDI call in fVDI to accomplish this, however. -- | Why are these | e-mail: johan@klockars.net | .signatures | | so hard to do | WWW: http://www.klockars.net | well? | (fVDI, MGIFv5, QLem)