This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
Mouse cursor shape ignores radar #3283
Labels
Milestone
Comments
|
Cyp commented Also, reported by Berg, clicking on the mini-map makes it start scrolling to the clicked location, but it doesn't finish scrolling. Bisect blames both problems on 6e0c364c99f8c85b5be96087059db7f627c2d3bc. |
|
cybersphinx changed status from |
|
cybersphinx changed resolution from `` to |
|
cybersphinx commented Move radar handling from processInput() to processRadarInput(). Fixes #3283.
|
|
cybersphinx commented Move radar handling from processInput() to processRadarInput(). Fixes #3283.
|
2 similar comments
|
cybersphinx commented Move radar handling from processInput() to processRadarInput(). Fixes #3283.
|
|
cybersphinx commented Move radar handling from processInput() to processRadarInput(). Fixes #3283.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
resolution_fixedtype_bug| by CypNoticed this when playing a multiplayer 1v1 in β5:
Seems the mouse cursor is whatever it would have been, if the radar wasn't there. If the cursor is a big "X" over certain terrain, then moving the viewport so the radar covers it, the cursor still shows a big "X". (Which is confusing.)
Should either show an arrow, or show what the cursor would be over the corresponding terrain where the radar refers to.
Issue migrated from trac:3283 at 2022-04-16 09:35:48 -0700
The text was updated successfully, but these errors were encountered: