<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 01/-10/-28163 11:59 AM, todd rme wrote:
<blockquote
cite="mid:%3CAANLkTimKLmWyWf7nzNnU3Kc6UKFO9q_0SdJJSMwX3j1A@mail.gmail.com%3E"
type="cite">
<div class="gmail_quote">On Sun, Feb 20, 2011 at 4:57 PM, Rick
Stockton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rickstockton@reno-computerhelp.com">rickstockton@reno-computerhelp.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> Within Qt, the Devs
have recognized that Button8 and Button9 are frequently
implemented "backwards". Thus they assigned the more cryptic
names "XButton1" and "XButton2".<br>
</div>
</blockquote>
</div>
<br>
Are you sure about this? I thought xbutton1 and xbutton2 where
the "buttons" for the x-axis, that is the scroll wheel. In other
words, xbutton1 is scroll up and xbutton 2 is scroll down (or vice
versus).<br>
</blockquote>
Yes. Within 'qt/src/gui/kernel/qapplication_x11.cpp' , where X11
mouse events undergo translation (within
QETWidget::translateMouseEvent(), which starts at-or-near line 4156
of the current GIT pull) you'll see Button4, Button5, Button6 and
Button7 handled together as wheel events (with compression). The
case statements for Button1 thru Button3 are above the wheel code,
and the case statements for Button8 and Button9 are below.<br>
<br>
BTW, the switch statement is being done on an unsigned int
(event->xbutton.button). Code for the higher-numbered buttons
doesn't bother to create names like "Button3", the lines simply
specify the uint values directly.<br>
-----<br>
I've mis-stated this in the past. Thanks for the question, creating
an opportunity for me to clarify and correct.<br>
<br>
</body>
</html>