-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimap out of sync #1657
Comments
Can you provide more details? This is why we have the templates to prompt for more information. Any screenshots, means to reproduce, version of the client? I'm in LT76 with you and am having no issues. I am running current |
Confirmed by multiple users, still unable to reproduce on my end. Suggestion that this is caused by device scaling seems contradicted by one affected user not using it. |
I turned scaling on my Kubuntu 22.04 laptop to 125% and the minimap is fine for me as well. Definitely need more details to understand this issue. I'm adding untriaged back until we have a way to reproduce. |
Observed strange results today when zooming the map, maybe this is related |
@wieder-fi says it happens after |
@hugomflavio found it's related to switching games. Could reproduce. |
The widget needs to compute horizontal and vertical scaling factors to map between the displayed minimap (in pixel units) and the computed one (essentially in tile units). It was computing them on resize events and storing them, which was causing issues when switching maps. Compute them when they are needed instead, it's just two float divisions. Also remove a bunch of unused variables from the class. Closes longturn#1657.
The widget needs to compute horizontal and vertical scaling factors to map between the displayed minimap (in pixel units) and the computed one (essentially in tile units). It was computing them on resize events and storing them, which was causing issues when switching maps. Compute them when they are needed instead, it's just two float divisions. Also remove a bunch of unused variables from the class and don't try to move() it when shown (it's in a layout). Closes longturn#1657.
Clicking on the minimap does not jump you to where you click, and the frame that represents the current view in the minimap also is not where you are.
It happened for me in LT75 and is like that from start in LT76.
The text was updated successfully, but these errors were encountered: