tablet mouse mousemove events are firing when should not #91325

New Issue

Jakub Uhlik · 2021-09-10T22:21:47+02:00

Jakub Uhlik commented

2021-09-10 22:21:47 +02:00

System Information
Operating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-06 16:56, hash: d7d8eb7de4
Worked: not tested

Short description of error
tablet mouse mousemove events are firing when should not

Exact steps for others to reproduce the error
tablet mouse mousemove events are firing when should not, i.e. when pen is pressed down, not moving, at full force to max out pressure and holding with both hands to prevent tilting (and verifying by numbers that it is). to repeat have a wacom, run code, watch terminal, press pen on tablet and prevent it moving. with regular mouse mouse move events are not firing when mouse is not moved so i think tablet pen when is not moved, its pressure or tilt is not changed should behave the same..

import bpy
from mathutils import Vector


class ModalOperator(bpy.types.Operator):
    bl_idname = "object.modal_operator"
    bl_label = "Simple Modal Operator"
    
    def modal(self, context, event):
        if(event.type == 'MOUSEMOVE'):
            if(event.is_tablet):
                print(event.type, event.mouse_x, event.mouse_y, event.pressure, event.tilt.x, event.tilt.y, )
                if(self.mouse_x == event.mouse_x and self.mouse_y == event.mouse_y and event.tilt == self.tilt and event.pressure == self.pressure):
                    #
                    - should not fire mouse move event while everything is the same? like with regular mouse..
                    #
                    print("!" * 100)
                else:
                    print(".")
                
                self.tilt = event.tilt
                self.pressure = event.pressure
                self.mouse_x = event.mouse_x
                self.mouse_y = event.mouse_y
        
        elif(event.type in {'ESC', }):
            return {'CANCELLED'}
        
        return {'RUNNING_MODAL'}
    
    def invoke(self, context, event):
        self.mouse_x = 0.0
        self.mouse_y = 0.0
        self.pressure = 1.0
        self.tilt = Vector()
        context.window_manager.modal_handler_add(self)
        return {'RUNNING_MODAL'}


def register():
    bpy.utils.register_class(ModalOperator)


def unregister():
    bpy.utils.unregister_class(ModalOperator)


if __name__ == "__main__":
    register()
    
    # test call
    bpy.ops.object.modal_operator('INVOKE_DEFAULT')

**System Information** Operating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-06 16:56, hash: `d7d8eb7de4` Worked: not tested **Short description of error** tablet mouse mousemove events are firing when should not **Exact steps for others to reproduce the error** tablet mouse mousemove events are firing when should not, i.e. when pen is pressed down, not moving, at full force to max out pressure and holding with both hands to prevent tilting (and verifying by numbers that it is). to repeat have a wacom, run code, watch terminal, press pen on tablet and prevent it moving. with regular mouse mouse move events are not firing when mouse is not moved so i think tablet pen when is not moved, its pressure or tilt is not changed should behave the same.. ``` import bpy from mathutils import Vector class ModalOperator(bpy.types.Operator): bl_idname = "object.modal_operator" bl_label = "Simple Modal Operator" def modal(self, context, event): if(event.type == 'MOUSEMOVE'): if(event.is_tablet): print(event.type, event.mouse_x, event.mouse_y, event.pressure, event.tilt.x, event.tilt.y, ) if(self.mouse_x == event.mouse_x and self.mouse_y == event.mouse_y and event.tilt == self.tilt and event.pressure == self.pressure): # - should not fire mouse move event while everything is the same? like with regular mouse.. # print("!" * 100) else: print(".") self.tilt = event.tilt self.pressure = event.pressure self.mouse_x = event.mouse_x self.mouse_y = event.mouse_y elif(event.type in {'ESC', }): return {'CANCELLED'} return {'RUNNING_MODAL'} def invoke(self, context, event): self.mouse_x = 0.0 self.mouse_y = 0.0 self.pressure = 1.0 self.tilt = Vector() context.window_manager.modal_handler_add(self) return {'RUNNING_MODAL'} def register(): bpy.utils.register_class(ModalOperator) def unregister(): bpy.utils.unregister_class(ModalOperator) if __name__ == "__main__": register() # test call bpy.ops.object.modal_operator('INVOKE_DEFAULT') ```

Jakub Uhlik commented

2021-09-10 22:21:47 +02:00

Added subscriber: @JakubUhlik

Yevgeny Makarov commented

2021-12-22 22:55:19 +01:00

Added subscriber: @jenkm

Yevgeny Makarov commented

2021-12-22 22:55:19 +01:00

Not sure how you detect that the pen is not moving. There may be tiny movements, less than a pixel.
You can easily have a series of events with the same coordinates. I'm able to get it with both a mouse and a trackpad.

Not sure how you detect that the pen is not moving. There may be tiny movements, less than a pixel. You can easily have a series of events with the same coordinates. I'm able to get it with both a mouse and a trackpad.

Jakub Uhlik commented

2021-12-25 19:15:08 +01:00

it is not a problem of coordinates, but that the event is firing, no change should be no event i guess. another test, i took myself from equation, made L from boxes, put pen in corner, nothing moved, no change in pressure, no change in tilt, many many events firing constantly. would be nice if somebody can replicate that with maybe less well used tablet. mine might be faulty after years of use..

Yevgeny Makarov commented

2022-01-04 17:49:39 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Yevgeny Makarov commented

2022-01-04 17:49:39 +01:00

Yeah, I see what you mean, checked with Wacom CTL-4100. But it seems to me this is the expected behavior, the driver fire events with a certain frequency, events can be identical. And I don't see any problems with drawing or sculpting modes.

Definitely not related to the "Python API", maybe someone from the "User Interface" team will explain how it should be.

Yeah, I see what you mean, checked with Wacom CTL-4100. But it seems to me this is the expected behavior, the driver fire events with a certain frequency, events can be identical. And I don't see any problems with drawing or sculpting modes. Definitely not related to the "Python API", maybe someone from the "User Interface" team will explain how it should be.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

tablet mouse mousemove events are firing when should not #91325