From: david jeannot <djeannot24@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port: cocoa programmer needed
Date: Fri, 26 Aug 2011 19:05:00 +0200 [thread overview]
Message-ID: <CA+N9rYmY30D=rwstgf3XzhD0Dsj8WxPFGby7b6YYV=BdCZ5vdg@mail.gmail.com> (raw)
In-Reply-To: <CADSkJJUFAuqbnxPea=pETR115nUw56-fBY=8NhG1gAGxahyV_Q@mail.gmail.com>
> This sounds very cool. Did you figure out a way
> to let acme move the mouse cursor the way it wants
> to?
Yes: Devdraw's setmouse() is implemented.
Yesterday I said: "There is just the bare minimum".
I should have said: "There is almost everything if
you use OS X Lion". (There is still mouse
support, the alt and cmd keys still simulate mouse
buttons, etc.)
A thing that annoy me since yesterday is that a
cut (cmd+x) immediately followed by a paste
(cmd+v) leaves a "clean" Acme's window "dirty".
We could maybe send a cmd+u instead of a cmd+v
when the fingers remain on the tactile device
between the left-swipe and the right-swipe, that
Acme would interpret as "Undo", if there is no
simpler way. Or we could just use another gesture
to copy (cmd+c), but there would be no feedback.
Another thing that annoy me is that I receive
swipe-up and swipe-down events only if I disable
the OS X application BetterTouchTool, that I
configured to instruct Google Chrome, and Google
Chrome only, to create a new tab when I swipe-up,
and to close the current tab when I swipe-down.
Does anyone know how BetterTouchTool is
implemented? A BetterTouchTool-like 9p server
might be a good solution :)
next prev parent reply other threads:[~2011-08-26 17:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 20:31 Russ Cox
2011-08-03 4:25 ` David Leimbach
2011-08-03 12:52 ` Russ Cox
2011-08-07 22:14 ` David Leimbach
2011-08-07 23:59 ` [9fans] " andrey mirtchovski
2011-08-25 18:33 ` david jeannot
2011-08-25 19:09 ` Russ Cox
2011-08-25 20:35 ` David Leimbach
2011-08-26 14:11 ` Russ Cox
2011-08-26 17:05 ` david jeannot [this message]
2011-08-27 18:31 ` david jeannot
2011-08-28 2:40 ` Russ Cox
2011-08-28 10:14 ` david jeannot
2011-09-04 9:51 ` david jeannot
2011-09-06 14:16 ` Russ Cox
2011-09-06 15:47 ` David Leimbach
2011-09-06 15:52 ` Aram Hăvărneanu
2011-09-06 16:03 ` Russ Cox
2011-09-06 16:25 ` Aram Hăvărneanu
2011-09-06 18:34 ` Latchesar Ionkov
2011-09-06 18:54 ` David Leimbach
2011-09-06 19:18 ` Latchesar Ionkov
2011-09-06 19:37 ` Russ Cox
2011-09-06 19:41 ` david jeannot
2011-09-06 19:41 ` David Leimbach
2011-09-06 19:42 ` David Leimbach
2011-09-06 19:43 ` andrey mirtchovski
2011-09-06 19:45 ` andrey mirtchovski
2011-09-06 20:17 ` david jeannot
2011-09-06 20:23 ` andrey mirtchovski
2011-09-13 15:59 ` david jeannot
2011-09-13 17:22 ` David Leimbach
2011-09-14 14:29 ` Jeff Sickel
2011-09-14 16:40 ` david jeannot
2011-09-14 16:57 ` hiro
2011-09-14 17:17 ` John Floren
2011-09-14 17:23 ` andrey mirtchovski
2011-09-14 17:28 ` David Leimbach
2011-09-14 17:31 ` ron minnich
2011-09-14 17:34 ` David Leimbach
2011-09-14 17:48 ` andrey mirtchovski
2011-09-14 18:10 ` david jeannot
2011-09-14 19:29 ` david jeannot
2011-09-14 22:34 ` david jeannot
2011-09-14 23:20 ` hiro
2011-09-06 16:26 ` Jeff Sickel
2011-09-06 17:21 ` David Leimbach
2011-08-26 16:56 ` Salman Aljammaz
2011-08-26 8:53 ` Steve McCoy
2011-08-03 18:01 ` Jeff Sickel
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='CA+N9rYmY30D=rwstgf3XzhD0Dsj8WxPFGby7b6YYV=BdCZ5vdg@mail.gmail.com' \
--to=djeannot24@gmail.com \
--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).