bugssearch
advanced
using as
guest		loginabouthelp

 

Bug ID:  863  Allow the movement area to be defined for chords (etc.) for "unblock when the mouse moves"    
 
Created by phil on 2024-04-01 11:23 AM, 37 days ago
Project:  XMBC
Organization:  Development
Category:  enhancement
Priority:  high
Assigned to:  phil  
Status:  test
Target Release:Next Release
Version:Current Beta
 
 

show inline images      show change history

 comment 4416 posted by phil on 2024-04-01 8:29 PM, 36 days ago 

Also note, that when aborting, the cursor should move back to where it started, then perform the abort action (button down) then move to where it was aborted again - thus not causing any issues when dragging on a chorded button.

Rigth now it does not work as intended (and is particually noticable when the pixel movement to abort is set to a high number.
 comment 4414 posted by phil on 2024-04-01 2:36 PM, 37 days ago 

The back end already supports this, just the GUI needs updating!
 comment 4406 posted by phil on 2024-04-01 11:23 AM, 37 days ago 

Allow the user to define how far the mouse has to move - right now its hard coded to (I think) 5 pixels. Some mice are more sensative/wobbly and it would be nice to be able to increase this (not globally but per definition!).

 

Me myself raised this, because ot sensitivity on the settlers chord on the G604/Surface