Hmm...replying to myself.  That can't be good.  :-)

On Mon, 11 Oct 2004 10:05:39 -0600, Elijah Newren <newren gmail com> wrote:
> On Mon, 11 Oct 2004 17:00:13 +0200, Lubos Lunak <l lunak suse cz> wrote:

> >  This probably shouldn't have so strong wording. Getting every single widget
> > which can handle mouse press+move+release to report correct type can be a lot
> > of work. My Qt patch doing only the old way (i.e. only MISC) is a couple of
> > lines, supporting all this won't be. Maybe only supporting MISC should be
> > called a simple support or so? After all, I don't know about others, but I'd
> > only rarely need this feature, so I wonder if developers would consider this
> > to be worth the trouble.

Actually, the more I think about it, the more I wouldn't mind saying
that usage of MISC is fine for simple support.  That would allow for
basic behavior that mimics TAKE_ACTIVITY, and I think that would
improve things.  Granted, the system wouldn't feel as integrated as if
all toolkits had full support, but I think it would behave better than
having some toolkits with full support and some with no support.  So I
take back my objections to this.

There is another issue I have thought of that could potentially be
problematic:  Text selection can often be done via double-click (to
select a word) or triple-click (to select a full line).  Yet a double
click will act like ButtonPress, ButtonRelease, ButtonPress,
ButtonRelease--resulting in the window being raised after the first
ButtonRelease.  Does anyone see a clean way to support text-selection
without raising using double and triple clicks?  I'm not sure it's a
big deal, but I'd like to cover all cases if possible.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]