Apple Magic Mouse returns event.value NOTHING instead of NORTH or SOUTH #79376

Closed
opened 2020-07-29 21:09:50 +02:00 by MACHIN3 · 9 comments

System Information
Operating system: Linux-4.15.0-108-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21

Blender Version
Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd749
Worked: (newest version of Blender that worked as expected)

Short description of error
Using the touchpad of the Apple Magic Mouse 2 to scroll returns the event.value NOTHING instead of NORTH or SOUTH.

I'm attaching a blend file with a simple script to output input event.type and event.value to the terminal.

input_events.blend

Exact steps for others to reproduce the error

  • on MacOS with a Magic Mouse 2 open the attached blend file and run the script from the Scripting workspace
  • use the tough pad on the mouse to swipe up or down
  • the terminal will print TRACKPADPAN NOTHING
  • I'd expect it to print TRACKPADPAN NORTH or TRACKPADPAN SOUTH
**System Information** Operating system: Linux-4.15.0-108-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21 **Blender Version** Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: `353e5bd749` Worked: (newest version of Blender that worked as expected) **Short description of error** Using the touchpad of the Apple Magic Mouse 2 to scroll returns the event.value NOTHING instead of NORTH or SOUTH. I'm attaching a blend file with a simple script to output input event.type and event.value to the terminal. [input_events.blend](https://archive.blender.org/developer/F8729192/input_events.blend) **Exact steps for others to reproduce the error** * on MacOS with a Magic Mouse 2 open the attached blend file and run the script from the Scripting workspace * use the tough pad on the mouse to swipe up or down * the terminal will print `TRACKPADPAN NOTHING` * I'd expect it to print `TRACKPADPAN NORTH` or `TRACKPADPAN SOUTH`
Author

Added subscriber: @MACHIN3

Added subscriber: @MACHIN3

Added subscriber: @Khrooma

Added subscriber: @Khrooma

System Information
Operating system: macOS Catalina 10.15.6
Graphics card: Intel Iris Plus Graphics 645 1536MB / eGPU Razer Core - Gigabyte Radeon Rx 5700 Gaming OC 8G PCIe 4.0, 8GB 256-Bit GDDR6, Gv-R57GAMING OC-8GD Video Card

Blender Version
Broken: version: 2.83.3

I can confirm, got the error using a Magic Mouse 2 and following the exact same steps listed.

**System Information** Operating system: macOS Catalina 10.15.6 Graphics card: Intel Iris Plus Graphics 645 1536MB / eGPU Razer Core - Gigabyte Radeon Rx 5700 Gaming OC 8G PCIe 4.0, 8GB 256-Bit GDDR6, Gv-R57GAMING OC-8GD Video Card **Blender Version** Broken: version: 2.83.3 I can confirm, got the error using a Magic Mouse 2 and following the exact same steps listed.

Added subscriber: @jenkm

Added subscriber: @jenkm

These NORTH, SOUTH, ... these are for TWEAK events.

Trackpad events always event.val = KM_NOTHING.
Try to look at event.x, event.y, event.prevx, event.prevy.

There is no bug here.

These `NORTH`, `SOUTH`, ... these are for `TWEAK` events. Trackpad events always `event.val = KM_NOTHING`. Try to look at `event.x`, `event.y`, `event.prevx`, `event.prevy`. There is no bug here.
Author

In #79376#987566, @jenkm wrote:
These NORTH, SOUTH, ... these are for TWEAK events.

Trackpad events always event.val = KM_NOTHING.
Try to look at event.x, event.y, event.prevx, event.prevy.

There is no bug here.

I suspected as much. I was hoping I could treat these trackpad events just like WHEELUPMOUSE and WHEELDOWNMOUSE, as single events, so I can fallback to use these if a mouse with scroll wheel is not available.
Comparing event.y with event.prev.y to determine the direction seems awkward, if at all possible. I don't actually want the trackpad to affect the mouse position.

> In #79376#987566, @jenkm wrote: > These `NORTH`, `SOUTH`, ... these are for `TWEAK` events. > > Trackpad events always `event.val = KM_NOTHING`. > Try to look at `event.x`, `event.y`, `event.prevx`, `event.prevy`. > > There is no bug here. I suspected as much. I was hoping I could treat these trackpad events just like WHEELUPMOUSE and WHEELDOWNMOUSE, as single events, so I can fallback to use these if a mouse with scroll wheel is not available. Comparing event.y with event.prev.y to determine the direction seems awkward, if at all possible. I don't actually want the trackpad to affect the mouse position.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Richard Antalik self-assigned this 2020-08-01 23:42:57 +02:00

I will believe @jenkm and will close this.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

I will believe @jenkm and will close this. Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#79376
No description provided.