Bug 18475 - Bad mapping for Right-Click on PowerPC
Summary: Bad mapping for Right-Click on PowerPC
Status: RESOLVED MOVED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xkb
QA Contact:
URL: https://bugs.edge.launchpad.net/ubunt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-10 21:32 UTC by Bryce Harrington
Modified: 2018-12-28 00:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Bryce Harrington 2008-11-10 21:32:27 UTC
Forwarding this bug report from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/46378

On Macbooks, the right mouse button is mapped to the F12 key, however on recent model Macbooks the F12 key is no longer present on the standard keyboard (requires the Fn key now), making this particularly troublesome now.

A re-mapping of the right mouse button would be worthwhile even for older macbooks, as the current mapping has been a source of confusion among powerbook users for quite some time.

The Debian MacBook guide includes a suggestion of using the left "Command" key as the right mouse button.  http://wiki.debian.org/MacBook .  We'd like to know what upstream would think of this idea, or if a different idea would be better?
Comment 1 Sergey V. Udaltsov 2008-12-28 17:47:17 UTC
XKB cannot map keys to mouse buttons. You can try convincing people dealing with evdev driver to provide you with some special option (in xorg.conf) - in that case, feel free to reopen the bug and assign to product xorg, component Input/Evdev or smth
Comment 2 Alan Coopersmith 2008-12-29 20:47:12 UTC
XKB has a limited ability to map keys to mouse buttons/movements through 
mousekeys:
http://cgit.freedesktop.org/xkeyboard-config/tree/compat/mousekeys

or as described in the Debian Wiki link:
xmodmap -e "keycode 115 = Pointer_Button3"
Comment 3 Sergey V. Udaltsov 2008-12-30 03:50:45 UTC
Oops. Right. Sorry, I totally forgot about mousekeys. Have to think about it again.

Thanks, Alan
Comment 4 Sergey V. Udaltsov 2009-01-02 10:58:38 UTC
I've just tried to map LWIN to Pointer_Button3. It works in a sense that xev displays that keysym. But Firefox does not react on that "button". Neither other apps.

In the interpret section, I see 

    interpret Pointer_Button3+AnyOfOrNone(all) {
        action= PtrBtn(button=3);
    };

which looks logical. Anything I am missing?

PS Just checked, Shift+Numlock switched me ok into working mousekeys mode.
Comment 5 GitLab Migration User 2018-12-28 00:38:21 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/66.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.