From kde-bugs-dist Tue Dec 14 08:42:16 2010 From: rickst29 Date: Tue, 14 Dec 2010 08:42:16 +0000 To: kde-bugs-dist Subject: [Bug 34362] support for additional mouse buttons Message-Id: <20101214084216.69B637593B () immanuel ! kde ! org> X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=129231613922127 https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #30 from rickst29 2010-12-14 09:41:52 --- status update. After a helpful discussion with some late-night qt Devs on their IRC channel, I have just opened a bug with qt -- and I intend to provide a functional, ready-for-review update for this "ancient" issue. (Both the code and the Doc.) No comments yet, not even extra info posted by me-- just the basic definition of the issue. http://bugreports.qt.nokia.com/browse/QTBUG-16092 Within X11, the "button" field of the typedef for XButtonPressedEvent and XButtonReleasedEvent is an unsigned int. *NOT* a bitmask, and the X11 mask field is limited to 5 bits. So, if a higher-numbered button is ALREADY in pressed State when the mouse enters your App Window, there's no way to advise you of that. We'll only be able to show a single button number for a "high-numbered" press or release which takes place within YOUR window, with masked state of buttons L, R, M, X1 and X1 (only!) provided in the too-small button mask field. Unsure whether I'll have to create a subclass to provide "extended" versions of the API. I'll SWAG that it will b necessary, for BC... there's just not enough bits left to play with. :(( -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.