From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mac multi-touch mice and p9p acme anyone?
Date: Fri, 27 Nov 2009 10:02:28 -0800 [thread overview]
Message-ID: <04953BC9-CEA0-4154-8A3E-FAE965AD6988@telus.net> (raw)
In-Reply-To: <4897B6D1-E7D7-45B1-A38D-64104AB53FC5@gmail.com>
Yes. It's a mod to devdraw that re-interprets mouse-down to mean "read the virtual buttons" and passes those along. The hardest part is adjusting the "landing zone" for the buttons - it turns out thirds isn't where I click :-)
It would be a good job throughout the desktop if I could figure out how to suppress delivery of the real button clicks (filter them out of the desktop event queue), but I've not managed that yet.
Paul
On 2009-11-27, at 8:35 AM, Eric Van Hensbergen wrote:
> Proper acme chords? I futzed with it before with the previous apple mice and couldn't get it to work. This with the new multitouch mice?
>
> -Eric
>
> Sent from my iPhone
>
> On Nov 26, 2009, at 1:58 AM, Paul Lalonde <plalonde@telus.net> wrote:
>
>> I wound up with one of these today, and I just had to mess with it enough to get chording working through the multi-touch interfaces. I have no idea how it behaves on a trackpad, but the top 20% of my magic mouse is now 3 separate buttons with reasonable tapping and chording behaviour. I can tar up my new devdraw for anyone who cares.
>>
>> I had to make a small change to the build system required to make this work as well. I had to add a -F/System/Library/PrivateFrameworks to the 9l script - where's the right place to do this for a single project?
>>
>> Paul
>>
>>
>
next prev parent reply other threads:[~2009-11-27 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 7:58 Paul Lalonde
2009-11-26 9:32 ` Lawrence E. Bakst
2009-11-27 16:35 ` Eric Van Hensbergen
2009-11-27 18:02 ` Paul Lalonde [this message]
2009-12-01 2:08 ` Eric Van Hensbergen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04953BC9-CEA0-4154-8A3E-FAE965AD6988@telus.net \
--to=plalonde@telus.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).