CodeAsm / open-sauce

Automatically exported from code.google.com/p/open-sauce
1 stars 1 forks source link

HUD scaling causes mouseover position of sorting tab and buttons in the multiplayer lobby to misposition #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Make sure high resolution is used. (1920x1080)
2. Make sure HUD scaling is on
3. Open the internet multiplayer lobby (gamespy)
3. Mouse over on the player, ping tabs or back button

What is the expected output? What do you see instead?
Expected is that the tabs highlight and are clickable on mouseover

Instead the tabs and buttons do no highlight unless the mouse is moved far too 
the right of the screen.

What version of the product are you using? On what operating system?
v3.0.0 on Windows 7

Please provide any additional information below.
N/A

Original issue reported on code.google.com by s...@halorank.com on 18 Jan 2012 at 10:01

GoogleCodeExporter commented 8 years ago
From the sound of it, this is related to the engine's widget system, and thus, 
the widget definitions.

We'll probably fix this by either disabling HUD scaling (which in this case is 
a misnomer) while at the mainmenu. We'll have to see how much, if any, this 
affects the in-game pause menus as well.

Original comment by kornma...@gmail.com on 18 Jan 2012 at 10:22

GoogleCodeExporter commented 8 years ago
This looks like the hud scaling matrix isn't being used when rendering the 
mouse cursor, so it is moving along the full width of the screen whilst the 
table is being scaled down to its 4:3 ratio.

Original comment by TheFieryScythe@gmail.com on 18 Jan 2012 at 10:39

GoogleCodeExporter commented 8 years ago
This also occurs on the credits screen, so may be related to the widget used to 
render dynamic text such as the server table in MP and the credits themselves.

Original comment by TheFieryScythe@gmail.com on 19 Jan 2012 at 12:34

GoogleCodeExporter commented 8 years ago
The cursor does not seem to go through the same rendering functions as other 
widgets, so scaling was not guaranteed to be on for it.

Fixed in revision 2712a8dbef74ad2b1c796391bb67dc5151c3fe0d (265)

Original comment by TheFieryScythe@gmail.com on 21 Jan 2012 at 1:12