[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] SV: Eiffel wheel mouse
- To: mint@lists.fishpool.fi
- Subject: Re: [MiNT] SV: Eiffel wheel mouse
- From: Vincent Rivière <vincent.riviere@freesbee.fr>
- Date: Fri, 20 May 2011 13:53:21 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mA8hkWkfB+dmWOBc6Jixm1+E0Yj3rBnbopsBsShYzsU=; b=AWHuyfk8BOxNaGylZizAcO491JZbyp+7pMvm8YAbmeqsQs8uJTaVMh5dQ3u6zhsQd1 UeXxq3MnwCOufaa7FbulIq9icFZIjEY4TLXbe1s6rrRo52JSa79QzV8yGJYQ8flbUCoF klTUa08o06HQ7fcSoLx3zLvEAw3wacsPB/Ai0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=fsLrTwVFeAEGVa/hbFX1vGtv7qx3ipBQo7iTAPoUMLWeQibQZIB2k50W/eT6H6XWWk +elwlUbcgThj/Q6xDyerIEXQ7BBqpNYZBGTUEjZmZHtcZhiVSdbOazunO7uh1IogREXO qw3BKJA4LR5R+zJy1PJHnVMvonFyVn8MeS9Ew=
- In-reply-to: <962067.295887636-sendEmail@descaro>
- List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
- List-id: <mint.lists.fishpool.fi>
- List-owner: <mailto:tjhukkan@fishpool.fi>
- List-post: <mailto:mint@lists.fishpool.fi>
- List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
- List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
- References: <962067.295887636-sendEmail@descaro>
- Sender: mint-bounce@lists.fishpool.fi
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
Helmut Karlowski wrote:
Does the VDI handle F16 as wheel-event?
I guess this is the problem... We can't assume that all the VDI
implementations understand the Eiffel wheel codes and support
vex_wheelv() :-(
I have added support for that inside the EmuTOS VDI some time ago :-)
Unfortunately the poor EmuTOS AES is unable to send scroll events from
the mouse handlers :-(
Don't bother, this is out of topic.
I intend to test for a modifier in XaAES to decide beween S-F6 and
F16. That's all I can imagine to do as long as keyboard is used to
transport wheel-events.
I propose do the following in XaAES:
- when EIFFEL_SUPPORT is off (the default), handle the wheel only
through the VDI vex_wheelv(), if available. That will work fine with any
hardware supported by the underlying VDI.
- when EIFFEL_SUPPORT is on, try to cope with a an old VDI lacking
support for Eiffel. As a side effet, Shift+F6 will be interpreted as a
wheel event instead of a keystroke. This is the current behavior.
This is the best we can do inside XaAES.
NB: I don't know how wheel status frames are currently handled.
--
Vincent Rivière