Bug 1309 - Mouse buttons not specified in BCM VC IV MouseEvents
Summary: Mouse buttons not specified in BCM VC IV MouseEvents
Status: RESOLVED FIXED
Alias: None
Product: Newt
Classification: JogAmp
Component: embedded (show other bugs)
Version: 2.4.0
Hardware: embedded_arm linux
: P4 normal
Assignee: Sven Gothel
URL:
Depends on:
Blocks:
 
Reported: 2016-05-22 18:56 CEST by Gottfried Haider
Modified: 2019-03-27 03:57 CET (History)
2 users (show)

See Also:
Type: DEFECT
SCM Refs:
jogl 60fadc1e723eaae471d68e9b0b939dfe2ba6abfe
Workaround: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gottfried Haider 2016-05-22 18:56:35 CEST 
Mouse events received using JOGL and the BCM VC IV (Raspberry Pi) driver don't specify the mouse button that was pressed or released. See e.g.:

MouseEvent[EVENT_MOUSE_CLICKED, [117]/[64], button 0, count 1, rotation [0.0, 0.0, 0.0] * 1.0, pointer<1>[0/Mouse: 117/64, p[0.0/1.0=0.0]], InputEvent[modifiers: [], NEWTEvent[source:jogamp.newt.driver.bcm.vc.iv.WindowDriver, consumed false, when:1463935695926 d 1ms]]]

Processing is looking at nativeEvent.getModifiers() to have the bits for BUTTON1_MASK, BUTTON2_MASK, or BUTTON3_MASK set.

Is this information somehow retrievable from Broadcom's driver? Thanks for looking into this!
Comment 1 Sven Gothel 2019-03-27 03:57:52 CET 
Gottfried, thank you for your patches. 
Very much appreciated.

I have merged your patch.
Since I don't test this platform - I trust you here.

Please reopen this bug if required.