Regresion: Can no longer infinite drag if the mouse hits an screen edge #113511

Closed
opened 2023-10-10 18:49:14 +02:00 by Guillermo Venegas · 8 comments
Contributor

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.42

Blender Version
Broken: version: 4.1.0 Alpha, commit date: 2023-10-10 16:27, hash: a565b586d912
Worked: (newest version of Blender that worked as expected)

Short description of error
Can no longer infinite drag if the mouse hits an screen edge

Exact steps for others to reproduce the error

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.42 **Blender Version** Broken: version: 4.1.0 Alpha, commit date: 2023-10-10 16:27, hash: `a565b586d912` Worked: (newest version of Blender that worked as expected) **Short description of error** Can no longer infinite drag if the mouse hits an screen edge **Exact steps for others to reproduce the error** <video src="/attachments/8fea864f-46c2-487e-adcf-2724765105f0" title="2023-10-10 10-48-15.mp4" controls></video>
Guillermo Venegas added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2023-10-10 18:49:15 +02:00
Author
Contributor
@Harley
Harley Acheson self-assigned this 2023-10-10 19:29:25 +02:00

Not sure if I can repro, there is some weird cursor wrapping behavior on linux though.

Not sure if I can repro, there is some weird cursor wrapping behavior on linux though.
Member

I can confirm. Reverting 1d141e721c fixes the continuous grab

I can confirm. Reverting 1d141e721c62a0cccf7341238fd03da81343095b fixes the continuous grab
Pratik Borhade added this to the 4.0 milestone 2023-10-11 05:19:26 +02:00
Member

@guishe

Just making sure we are seeing the same things. This is a problem when the mouse hits the desktop edge right? As in if you have multiple monitors it works okay in a middle monitor, just not at the desktop edges. And this is when the blender window's edge is exactly on the edge? Because if I pull the blender window just a pixel or two away from the edge then it works okay. Sound the same?

@iss - I'm assuming that the changes in 1d141e721c couldn't affect Linux at all. Are you seeing otherwise?

@guishe Just making sure we are seeing the same things. This is a problem when the mouse hits the desktop edge right? As in if you have multiple monitors it works okay in a middle monitor, just not at the desktop edges. And this is when the blender window's edge is exactly on the edge? Because if I pull the blender window just a pixel or two away from the edge then it works okay. Sound the same? @iss - I'm assuming that the changes in 1d141e721c62a0cccf7341238fd03da81343095b couldn't affect Linux at all. Are you seeing otherwise?

@iss - I'm assuming that the changes in 1d141e721c couldn't affect Linux at all. Are you seeing otherwise?

I did check with older versions and the behavior is consistent. It seems to fail to wrap cursor when going in direction where 2nd monitor is too fast. Don't have windows machine with 2 monitors atm to check.

> @iss - I'm assuming that the changes in 1d141e721c62a0cccf7341238fd03da81343095b couldn't affect Linux at all. Are you seeing otherwise? I did check with older versions and the behavior is consistent. It seems to fail to wrap cursor when going in direction where 2nd monitor is too fast. Don't have windows machine with 2 monitors atm to check.
Member

@iss I did check with older versions and the behavior is consistent

Thank you so much for testing. I couldn't see any way the changes could affect Linux, but I've been wrong before.

> @iss I did check with older versions and the behavior is consistent Thank you so much for testing. I couldn't see any way the changes could affect Linux, but I've been wrong before.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2023-10-12 01:04:05 +02:00
Author
Contributor

This is a problem when the mouse hits the desktop edge right?

And at the bottom too

Was the rectangle given by GetClientRect is used.
https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getclientrect#remarks
It says that the bottom and right coordinates count an exclusive pixel.

>>This is a problem when the mouse hits the desktop edge right? And at the bottom too Was the rectangle given by `GetClientRect` is used. https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getclientrect#remarks It says that the bottom and right coordinates count an exclusive pixel.
Member

And at the bottom too

Perfect. Thanks!

It says that the bottom and right coordinates count an exclusive pixel.

Yes, that issue probably screws up by a pixel in a bunch of places.

Not strictly for this though. In a nutshell the warping can occur outside of our window but not outside of the desktop bounds. So when our window is right against the outer edge we need some margin, enough for the cursor warping to occur. Now we are using a value that is 10% of the warping bounds width - and that applies in all directions.

> And at the bottom too Perfect. Thanks! > It says that the bottom and right coordinates count an exclusive pixel. Yes, that issue probably screws up by a pixel in a bunch of places. Not strictly for this though. In a nutshell the warping can occur outside of our window but not outside of the desktop bounds. So when our window is right against the outer edge we need some margin, enough for the cursor warping to occur. Now we are using a value that is 10% of the warping bounds width - and that applies in all directions.
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#113511
No description provided.