From mint-bounce@lists.fishpool.fi Sun Dec 28 15:13:45 2008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=MeM05SW0wGPexOW0+ezhUa4jFWSvNbi3vBlNJi98fnU=; b=R6PGBBpxkGz1cIoXuDEslQCPSyrBlWF051G8i0HBPkJ/1ZuUPB0+z8relIS+MLOZRa wSn4pN+gIQOUqAmtTDultftrbXxgEQg/46o+Vo3pkhcFssYb97+SatcXBPaCkXxWKPtF zUG6bwUhvfjiicXN7tnPLZ+ZctfDZRVgZRGL0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ISu5Lcr7QcnBP59zHDS9VbxOYXoUr/23jlpJL+gDN2M+Xj8CzfmqAhb6t3WAO22OF7 MKtpeiBgeDcgG0n5g5NxRPJn1YcTVSrzUWIIQ79VabVwYJGbrJV5STtbaIsKSzkE0Sdn M/yqFA/qKqt5Kev8bQ219EQh8gzGrkhDU8G2A= Message-ID: Date: Sun, 28 Dec 2008 21:12:11 +0100 From: "Johan Klockars" To: mint@lists.fishpool.fi Subject: Re: [MiNT] an urgent GEM question :-) In-Reply-To: <1230484807.6224.9.camel@joy> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1230022147.7318.6.camel@joy> <20081223172329.6b2125e8@phineus> <1230456363.6300.5.camel@joy> <1230484807.6224.9.camel@joy> X-Google-Sender-Auth: b78c94e437236d6f 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: List-subscribe: List-owner: List-post: > 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. I'd say it's more likely to actually use vsm_locator() (vrq_locator() doesn't return until you press a key or mouse button), but that's a matter of what values were passed to vsin_mode(), since that is the only difference between vrq_locator() and vsm_locator() (they have the same function number...). Still, these functions actually should be able to do what you want. I never noticed it before (and, no, I have not implemented them in fVDI yet), but they don't only return the mouse position, they also take an initial mouse position as input parameter... It is clear that vsm_locator(hnd, x, y, &dummy, &dummy, &dummy) is indeed supposed to put the mouse cursor (visible or not according to its current state) at x,y and return immediately. Anyway, these functions should work under fVDI (as long as you don't use your own mouse handler), since I actually pass them through to the underlying VDI (fVDI does not yet have any mouse driver of its own). > The comments under these functions' descriptions in > Compendium are most interesting ("don't use or you confuse AES" :) ;-) /Johan