--nextPart1782973.6iKHjJo4XG
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Aaron J. Seigo wrote:
>* secondary, if any, action to be taken

How about tertiary and quaternary actions? I'm not thinking here of wheel=20
events (which the spec supports by calling Wheel, but of those fancy mice=20
with more than the 5 standard buttons.

It's not that far-fetched to think of them: most laptop touchpads support=20
horizontal scrolling, which are usually keyed to buttons 6 and 7 on X11.=20
An application like a media player could use the primary wheel to control=20
playback volume, whereas the horizontal scrolling could be used for=20
seeking in the current track.

My point is: should the SecondaryActivation call provide extra=20
identification information? MMB would be ID =3D 0, button 6 would be ID =3D=
 1,=20
button 7 would be ID =3D 2.=20

In a theoretical system tray area with keyboard focus, I imagine Enter=20
would trigger Activation, the context menu button would trigger=20
ContextMenu, PgUp and PgDown would trigger Wheel, but there are a lot of=20
other keys available which could be used.

OTOH, if we do provide such ability, there will be applications making use=
=20
of it, which in turn means they'll have limited functionality if the=20
system tray supports less events.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart1782973.6iKHjJo4XG
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBJ8WkdM/XwBW70U1gRAlz2AJ9vCb+v265M5HHI/IqHZuJzAF1Z+QCgu7ws
ao0jmHbODarAsQcTjacsObY=
=Lzsm
-----END PGP SIGNATURE-----

--nextPart1782973.6iKHjJo4XG--