Bug 136849

Summary:	Disabling touchpad using syndock doesn't work
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Christian Boltz <suse-beta>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Christian Boltz 2005-12-04 13:11:45 UTC

I use SUSE Linux 10.0 with current YOU updates + ksynpatics 0.2.3 from supplementary (as suggested in bug 121681).

When I click "disable touchpad temporarily" in syndock's context menu, nothing happens (except the mneu item changes to "reenable touch pad" ;-)  - the touchpad is still active.

When I disable the touchpad in the touchpad kcontrol module, it is really disabled. Re-enabling also works from kcontrol.

My laptop is a Acer TravelMate 803 with synaptics touchpad.

Any ideas what is wrong?

Comment 1 Christian Boltz 2006-01-06 12:46:25 UTC

Works with KDE 3.5 from supplementary.

However, the menu is misleading. Menu items are:
(1) Disable touch pad temporarily
(2) Just disable tapping

(2) is misleading - when you click it, the tapping is *not* disabled - it just changes the mode, the menu text changes to "Disabling both motion and tapping". 

You still have to click (1) to actually disable the touchpad (or only tapping, depending on the selected mode).

Suggestion for *much* better usability: Change the menu to

(1)     Disable touch pad temporarily   (keep as is)
(2) [ ] Just disable tapping
(3) [x] Disabling both motion and tapping

(2) and (3) should act as mode switch, the selected mode should have a checkmark in front.

Maybe (1) could also have a checkmark instead of changing the menu text, but that's not really a problem.

Is this something you fix @SUSE or should I forward this report to bugs.kde.org?

Comment 2 Dirk Mueller 2006-01-08 19:31:09 UTC

please report the usability issue at bugs.kde.org. resolving as fixed because the rest works.

Comment 3 Christian Boltz 2006-01-08 22:12:26 UTC

OK. I reported the usability issue at http://bugs.kde.org/show_bug.cgi?id=119768