@x, @y translated to the axes of @device, or null if @device is the mouse.
the button which was pressed or released, numbered from 1 to 5. Normally button 1 is the left mouse button, 2 is the middle button, and 3 is the right button. On 2-button mice, the middle button can often be simulated by pressing both mouse buttons together.
the master device that the event originated from. Use gdk.event.Event.getSourceDevice to get the slave device.
true if the event was sent explicitly.
a bit-mask representing the state of the modifier keys (e.g. Control, Shift and Alt) and the pointer buttons. See #GdkModifierType.
the time of the event in milliseconds.
the type of the event (gdk.types.EventType.ButtonPress, gdk.types.EventType._2buttonPress, gdk.types.EventType._3buttonPress or gdk.types.EventType.ButtonRelease).
the window which received the event.
the x coordinate of the pointer relative to the window.
the x coordinate of the pointer relative to the root of the screen.
the y coordinate of the pointer relative to the window.
the y coordinate of the pointer relative to the root of the screen.
Used for button press and button release events. The @type field will be one of gdk.types.EventType.ButtonPress, gdk.types.EventType._2buttonPress, gdk.types.EventType._3buttonPress or gdk.types.EventType.ButtonRelease,
Double and triple-clicks result in a sequence of events being received. For double-clicks the order of events will be:
Note that the first click is received just like a normal button press, while the second click results in a gdk.types.EventType._2buttonPress being received just after the gdk.types.EventType.ButtonPress.
Triple-clicks are very similar to double-clicks, except that gdk.types.EventType._3buttonPress is inserted after the third click. The order of the events is:
For a double click to occur, the second button press must occur within 1/4 of a second of the first. For a triple click to occur, the third button press must also occur within 1/2 second of the first button press.