UI bug: joysticks need deadzones

phileday / whirligig-old-issues

Whirligig Media Player bug tracking

0 stars 0 forks source link

UI bug: joysticks need deadzones #12

Open phileday opened 5 years ago

phileday commented 5 years ago

Bug in controller edit screen: Sometimes when you open it, and open the drop down e.g. to change the B button to something else, the list scrolls down all the time. There is no way to stop it. Moving the right analog stick sometimes changes the direction in which it scrolls. The only way to fix that is to exit the settings view completely and return to the controller config. It looks like when the stick is even the least bit off center, and then returns to the center, that is not registered. The list never notices that the stick returned to the center. And therefore it continues scrolling, even if you let go of the stick.

cheater commented 4 years ago

this bug also happens in the browser. The joysticks, which you use as buttons, need to have a slightly larger deadzone, so they only trigger when the joystick is actually being pressed. The deadzone should be configurable separately for each joystick.

cheater commented 4 years ago

I would rename this bug to "UI bug: joysticks need deadzones"

phileday commented 4 years ago

What control is this happening with.

Increasing the deadzone causes the Index controller to stop working so I'll have to look at fixes it for individual controllers.

cheater commented 4 years ago

This is using an Xbox controller, and it's for when scrolling in the playlist, the file browser, and when scrolling the bindings in the keyboard/controller setup.

On Wed, Apr 1, 2020 at 5:26 PM phileday notifications@github.com wrote:

What control is this happening with.

Increasing the deadzone causes the Index controller to stop working so I'll have to look at fixes it for individual controllers.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phileday/whirligig/issues/12#issuecomment-607316403, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPWPQC2M37DDQGEROXBKLRKNMIZANCNFSM4H5ZC4MQ .

phileday commented 4 years ago

This should be fixed now in whirligig_early_access_v.4.8. When you said it was the gamepad I checked that and there was an error in the code that didn't reset it to zero. This wasn't a deadzone issue although the deadzone option has also been implemented so hopefully that should now be double fixed.

cheater commented 4 years ago

Oh, that might have been it, yes. I'll try it out.

On Sat, Apr 4, 2020 at 9:16 PM phileday notifications@github.com wrote:

This should be fixed now in whirligig_early_access_v.4.8. When you said it was the gamepad I checked that and there was an error in the code that didn't reset it to zero. This wasn't a deadzone issue although the deadzone option has also been implemented so hopefully that should now be double fixed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phileday/whirligig/issues/12#issuecomment-609076213, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPWPX2CXSAL63KFWLINATRK6BPZANCNFSM4H5ZC4MQ .

cheater commented 4 years ago

Fixed in 4.81, maybe also in 4.8.