From xemacs-m  Wed Sep 17 10:11:32 1997
Received: from wfdutilgw.ml.com (wfdutilf01.ml.com [206.3.74.31])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA10256
	for <xemacs-beta@xemacs.org>; Wed, 17 Sep 1997 10:11:31 -0500 (CDT)
Received: from ml1.ml.com ([199.201.57.130])
	by wfdutilgw.ml.com (8.8.5/8.8.5/MLgw-3.03) with ESMTP id LAA06878
	for <xemacs-beta@xemacs.org>; Wed, 17 Sep 1997 11:12:20 -0400 (EDT)
Received: from commpost.ml.com (commpost.ml.com [146.125.4.24])
	by ml1.ml.com (8.8.5/8.8.5/MLml4-2.07) with SMTP id LAA21263
	for <xemacs-beta@xemacs.org>; Wed, 17 Sep 1997 11:11:03 -0400 (EDT)
Received: from spssunp.spspme.ml.com (spssunp.spspme.ml.com [192.168.111.13]) by commpost.ml.com (8.6.12/8.6.12) with ESMTP id LAA07119 for <xemacs-beta@xemacs.org>; Wed, 17 Sep 1997 11:11:02 -0400
Received: by spssunp.spspme.ml.com (SMI-8.6/SMI-4.1)
	id LAA20803; Wed, 17 Sep 1997 11:11:02 -0400
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: [PATCH] `make-event' accepts arguments
References: <kigk9gg8zp6.fsf@jagor.srce.hr> <199709170223.WAA20747@M66-080-21.MIT.EDU> <ocrsov46nzu.fsf@ml.com> <kig4t7kc9k6.fsf@jagor.srce.hr>
X-Face: y,o:AU/bfCrS+zS/W"^puB!rT!G7?U1Mvp1Hd{6h^>X4@Xp5,|g+rG>4gv/iy^&x9`k#s!]X~{]Js>@A4c}4Z"Ct7=#1nPS:?mrWH8c#>$)>/Wc5yuX_OFO1(4cZM{LvsKWVQSl~/i>!n[-B*i-alq[/m\bsdy;W4p(_ic;$BE.oG@eJf@sr#x#}FT<=H8Ozu%g;JpVz:v_~vt[>ef/MeNeo3~D^R]]*bB7{HB|E1$wfMzw
X-Y-Zippy: Are we THERE yet?
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Colin Rafferty <craffert@ml.com>
Date: 17 Sep 1997 11:11:01 -0400
In-Reply-To: Hrvoje Niksic's message of "17 Sep 1997 16:13:45 +0200"
Message-ID: <ocrn2lc6kmy.fsf@ml.com>
Lines: 38
X-Mailer: Gnus v5.5/XEmacs 20.3(beta20) - "Tirana"

Hrvoje Niksic writes:
> Colin Rafferty <craffert@ml.com> writes:
>> For example, I don't use strokes (in fact, I don't use the mouse except
>> for X cutting and pasting).  However, I want to read strokesified mail.
>> I do not want to lose the middle mouse button just because I want to
>> read strokes.

> You won't.  The point David was trying to make is that a simple press
> and release of button2 will *always* be let to normal uses
> (x-insert-selection or whatever).  Only *dragging* of button2 will be
> read as a stroke.

I've just reread David's post, and you are certainly correct.  It is
intending to only take over button2-drag.

However, I still think that if writing strokes takes over anything, it
should be split.  In fact, what I would suggest is having two kinds of
strokes-using modes: continue to have the current method, and have
another file that does the button2-drag takeover.

I am still making the argument that I would want strokes to only take
over a global binding on specific request.

Now that I think of it though, I can see some ways that this can be very
cool.  For example, there are laptops where the display half contains
the hardware, the display is a touch-screen, and the keyboard can be
removed.

I could install Linux with XEmacs, design graffiti-like strokes
recognition, and use a pen on the touch-screen to take notes.

All I would need is an extra couple of strokes that toggle <control> and 
<meta>, and I can run XEmacs from a pen.  Very cool.

-- 
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

