I recently tried the SUSE 9.1 'live CD' after having used RH9 and MDK9 
long enough to have gotten used to double-clicking again.

Well, launching apps from a live CD is a slow affair (at least on my 
machine), and my double-click habit stuck me with having to wait for 2 
slow-loading apps before I could shut the extra one down.

I remember this from way back when Mandrake defaulted their KDE setup to 
be single-click based.  It's not *that* hard to break the double-click 
habit, but my question is "why do I have to"?

Isn't it possible for KDE (or QT, or whatever is handling the single vs. 
double click behavior) to ignore a second click on an icon or link if it 
falls within the double-click time interval?  If not, why not?  Is it a 
function of X-Windows' mouse handling?

Seriously, when I show my Linux system to a typical Windows user, they 
start double-clicking all over the place.  They do this even on Windows 
in places where it's not necessary (like links on web pages), but on 
Windows the 2nd click doesn't seem to do anything.  I guess if it did, 
they'd learn not to do it...  But it makes sense to me to ignore extra 
clicks if they come to soon (at least as an option).

Rob

Rob Yampolsky wrote:

> I recently tried the SUSE 9.1 'live CD' after having used RH9 and MDK9
> long enough to have gotten used to double-clicking again.
> 
> Well, launching apps from a live CD is a slow affair (at least on my
> machine), and my double-click habit stuck me with having to wait for 2
> slow-loading apps before I could shut the extra one down.
> 
> I remember this from way back when Mandrake defaulted their KDE setup to
> be single-click based.  It's not *that* hard to break the double-click
> habit, but my question is "why do I have to"?

You don't HAVE to double click...  It's just a matter of preference.. 
Personally, I prefer single clicking..

To change it, open the KDE control center, go to: Peripherals -> Mouse
Then, select the double click radio button...

You should explore the control center..  There are a whole bunch of
things you can do to change the look and performance of KDE.  You aren't
stuck with the default behavior. 

> You don't HAVE to double click...  It's just a matter of preference.. 
> Personally, I prefer single clicking..
> 
> To change it, open the KDE control center, go to: Peripherals -> Mouse
> Then, select the double click radio button...
> 
> You should explore the control center..  There are a whole bunch of
> things you can do to change the look and performance of KDE.  You aren't
> stuck with the default behavior. 
> 

You're missing my point.  I like having single-click as the default 
behavior, but I don't see the need to have that mess up a friend who 
occasionally uses my machine - or to freak out a newbie that doesn't 
understand the difference between single- and double-clicking.

What I really want to find out is whether it's possible to ignore the 
second click on a single-click-configured system if it comes within the 
doubleclick time window.  If that's not possible because of how 
X-Windows works, find.  If it is, it would be a nice bit of 
user-friendliness (that anyone who really wants to be able to click an 
icon twice within 1/2 second could turn off).

Rob

Rob Yampolsky adjusted his tin foil beanie and asbestos underwear to
write:

>
> You're missing my point.  I like having single-click as the default
> behavior, but I don't see the need to have that mess up a friend who
> occasionally uses my machine - or to freak out a newbie that doesn't
> understand the difference between single- and double-clicking.

Why not give them their own accounts with own settings for everything,
show them what a proper multi-user O/S is like :)

-- 
Mark
Iligitimi Non Carborundum!
Twixt hill and high water, N.Wales, UK
onfxvgpnvfr-ng-tzk-qbg-pb-hx

> 
> Why not give them their own accounts with own settings for everything,
> show them what a proper multi-user O/S is like :)
> 

I suppose I could do that.  I just don't understand why doubleclicks 
need to be treated as 2 single clicks on a single-click-based system.

Windows seems to ignore the second click on, say, a pushbutton that 
doesn't need it.  Now maybe that's being done by the application itself, 
but that ought to be where a toolkit like KDE/QT would shine.  Why not 
have a 'doubleclick behavior' setting that offers several options:
	. Require doubleclicks to activate icons.
	. Activate on single click and ignore doubleclicks.
	. Activate on single click and treat doubleclicks as 2 single clicks 
(though I can't imagine why anybody would select this).

My point is that probably nobody wants KDE launching apps twice if you 
happen to doubleclick.  Now you can tell me that I need to train myself, 
and perhaps I do.  But I still think it's nice for computers to stop you 
from doing stupid things.  I'm telling you that ex-Windows users 
doubleclick all the time, and they don't understand when and where it's 
unnecessary.  Once again, you can say, "well, this isn't Windows", but 
if there's a mistake you know perfectly well that a large group of users 
is going to make, and the 'fix' to save them from themselves isn't going 
to harm anybody else, then why not do it?

I'm beginning to understand why people get exasperated with Linux 
formus.  I'm not saying Linux stinks, and I'm not asking for a 
workaround.  I'm not a newbie.  I'm just making a suggestion (and am 
curious about how hard it would be to do and why).  I'm perfectly aware 
that what I'm suggesting may not be possible (or worth the effort for 
somebody to code).  If so, that's the answer I'm looking for.

>
>My point is that probably nobody wants KDE launching apps twice if you 
>happen to doubleclick. 

Why convolute code?  Two instances of a program is the expected result
of clicking something twice in a single click enviroment.  

I think that if you double click the something in the single click
enviroment KDE should load 4 instances just to train you to stop
clicking so much.

-Adam

ashelley@inlandkwpp.com wrote:
>>My point is that probably nobody wants KDE launching apps twice if you 
>>happen to doubleclick. 
> 
> 
> Why convolute code?  Two instances of a program is the expected result
> of clicking something twice in a single click enviroment.  
> 
> I think that if you double click the something in the single click
> enviroment KDE should load 4 instances just to train you to stop
> clicking so much.
> 
> -Adam

Oh, I see.  I'm completely wrong.  Sorry I asked.

Rob

Rob Yampolsky adjusted his tin foil beanie and asbestos underwear to
write:

Hi Rob,

Just for a bit of OT here:-

http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=6,727,830

It appears that M$ has applied for a patent on the double-click so you
can`t use it under linux without paying them :)

I will not comment on this patent as I don`t think it would get past the
censors

-- 
Mark
Iligitimi Non Carborundum!
Twixt hill and high water, N.Wales, UK
onfxvgpnvfr-ng-tzk-qbg-pb-hx

Rob Yampolsky wrote:

> Oh, I see.  I'm completely wrong.  Sorry I asked.

And didn't you get your wrists slapped :-)

Actually it is a very valid point because to this day a lot of MS users
still use double-click. From a purely technical point of view we should
have adjustable double-click delay for bouncing not to mention from an
Accessibilty point of view for people with disabilities.
We should note that KDE does supply this for keypresses along with sticky
keys and slow keys so why not the mouse.
Having said that; this is probably really a function of the xserver, not kde
and I would not be surprised if it already exists and a line just needs to
be added to XF86Config.

-- 
regards,
andrew

In comp.windows.x.kde, akar uttered these immortal words:

> Actually it is a very valid point because to this day a lot of MS users
> still use double-click. From a purely technical point of view we should
> have adjustable double-click delay for bouncing not to mention from an
> Accessibilty point of view for people with disabilities.
> We should note that KDE does supply this for keypresses along with sticky
> keys and slow keys so why not the mouse.
>
> Having said that; this is probably really a function of the xserver, not
> kde and I would not be surprised if it already exists and a line just
> needs to be added to XF86Config.

KDE seems to be lacking in mouse support. Maybe, as you say, it's because X
handles it but it would be nice to be able to configure extra mouse buttons
without having to mess around with imwheel (they've done it for keyboards
now so I've kicked xbindkeys off my system) and adjust the speed of the
pointer without having to edit XF86Config. I'm just getting lazy in my old
age I think. :-)

-- 
Andy.

Andy Fraser wrote:

> I'm just getting lazy in my old
> age I think. :-)
Aren't we all...  I would not be surprised if such a module is in the
pipeline, kde is really becoming the true front-end of linux and burying
all the linux config stuff, look at the fantastic job they did with
printers so it doesn't matter if you have cups lpd or whatever; Display
Xsettings etc.

Have you had a close look at KHotkeys? I dismissed it at first as redundant
but then I took a look at it and saw that it lets you do mouse gestures,
dcop calls, numerous extremely powerful and sophisticated things that I
haven't even worked out yet. Sheesh! and I thought it was for keyboard
shortcuts.
-- 
regards,
andrew

In comp.windows.x.kde, akar uttered these immortal words:

> Have you had a close look at KHotkeys?

I've made extensive use of KHotkeys. :-)

> I dismissed it at first as 
> redundant but then I took a look at it and saw that it lets you do mouse
> gestures, dcop calls, numerous extremely powerful and sophisticated things
> that I haven't even worked out yet. Sheesh! and I thought it was for
> keyboard shortcuts.

It's very powerful and has my keyboard doing everything I want. Being able
to send DCOP calls is a really good feature. I can't get mouse gestures to
work though but I haven't really tried that hard.

-- 
Andy.

In comp.windows.x.kde, Andy Fraser uttered these immortal words:

>> Have you had a close look at KHotkeys?
> 
> I've made extensive use of KHotkeys. :-)
> 
>> I dismissed it at first as
>> redundant but then I took a look at it and saw that it lets you do mouse
>> gestures, dcop calls, numerous extremely powerful and sophisticated
>> things that I haven't even worked out yet. Sheesh! and I thought it was
>> for keyboard shortcuts.
> 
> It's very powerful and has my keyboard doing everything I want. Being able
> to send DCOP calls is a really good feature. I can't get mouse gestures to
> work though but I haven't really tried that hard.

And now they're working. I just thought I'd have another look at gestures
and noticed the khotkeys daemon wasn't running.

-- 
Andy.