Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Absolute scroll binding doesn't work at all #31756

Closed
LittleLilyBun opened this issue Feb 1, 2025 · 5 comments
Closed

Absolute scroll binding doesn't work at all #31756

LittleLilyBun opened this issue Feb 1, 2025 · 5 comments
Assignees

Comments

@LittleLilyBun
Copy link

Type

Game behaviour

Bug description

Clearing the absolute scroll binding should disable absolute scrolling, and changing the absolute scroll binding to something else (eg: M4) should allow absolute scrolling using that new binding. Instead, you can always absolute scroll with M2, when if the binding is changed, and custom bindings do nothing at all.

Checked on both Linux and Android, and the issue occurs on both.

Screenshots or videos

GitHub keeps failing the upload, so I have a YouTube link instead: https://youtu.be/njGravCGX1k

Version

2025.118.3-lazer

Logs

compressed-logs.zip

@peppy
Copy link
Member

peppy commented Feb 3, 2025

Yes, this is the best effort implementation due to limitations of our framework.

Tread the settings binding as a secondary binding, not a replacement. Right mouse will always work (and this is not expected to change).

@peppy peppy closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2025
@LittleLilyBun
Copy link
Author

Thing is, it doesn't serve its purpose as a secondary binding, when I set the binding to M4 I can't scroll with M4.

@peppy
Copy link
Member

peppy commented Feb 4, 2025

Does it work with other keys? Is it only not working with a mouse button?

@LittleLilyBun
Copy link
Author

I tried with various bindings (LCtrl, LCtrl+S, S, Tab, Space, F7) and none of them worked.

@peppy
Copy link
Member

peppy commented Feb 5, 2025

Right, I think this is due to the issue being hotfixed in the latest hotfix release. As in, the functionality is disabled right now. It should work again in the next actual release without any further changes from your end (I've confirmed the keys you tested above do work on my development build).

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants