Re: Multiplicity and Asininity in Tkinter Event API

References	<faec2643-7be7-4c92-80d2-e10592af2c17@v7g2000vbk.googlegroups.com> <mailman.1045.1310710680.1164.python-list@python.org> <6560d2cc-531e-4346-a2f6-fddb2635f44f@p14g2000yqj.googlegroups.com>
Date	2011-07-16 00:02 +1000
Subject	Re: Multiplicity and Asininity in Tkinter Event API
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.1064.1310738549.1164.python-list@python.org> (permalink)

Show all headers | View raw

On Fri, Jul 15, 2011 at 11:54 PM, rantingrick <rantingrick@gmail.com> wrote:
> Ok Mr. Pedantic. I suppose for unity sake we should use the sequence
> name "<MousePress>" instead of <MouseClick>. I'll give you that one.
>

It is very significant; if you call it Click, people will assume it
means Press, Release within a certain maximum time and without more
than a maximum amount of movement (in some cases 0 movement, others
permit a mickey or two).

Yes, that's all that's actually needed. But if you force programmers
to process the low-level events, you put load on them that they don't
need. It's possible to define every program in terms of a handful of
operations - do you want to ditch all of Python's rich syntax and
library in favour of that?

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Multiplicity and Asininity in Tkinter Event API rantingrick <rantingrick@gmail.com> - 2011-07-14 15:34 -0700
  Re: Multiplicity and Asininity in Tkinter Event API Chris Angelico <rosuav@gmail.com> - 2011-07-15 16:17 +1000
    Re: Multiplicity and Asininity in Tkinter Event API rantingrick <rantingrick@gmail.com> - 2011-07-15 06:54 -0700
      Re: Multiplicity and Asininity in Tkinter Event API Chris Angelico <rosuav@gmail.com> - 2011-07-16 00:02 +1000

csiph-web