search

google-code-export / project6014

Automatically exported from code.google.com/p/project6014
0 stars 0 forks source link

StarMap destinatin planet selection is glitchy #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Go to Beta Naos
2. Open starmap.
3. Try to select Sol as destination.

What is the expected output? What do you see instead?
I expect to select Sol, but instead Rigel is selected.

What version of the product are you using? On what operating system?
Demo 0.2.1 and hiresx4, win 7x64 (1920*1200 FullScreen). 

Please provide any additional information below.
I can select Sol by offsetting the cursor to the left and down a little.

Also the cursor in starmap mode is moving too slowly.
I think that it shouldn't move pixel by pixel, but rather by the size of the 
smallest star (star sprite|image). In SC2 the star grid was equal to 1px, and 
the cursor step was 1px also.
In hires mode the cursor still steps by 1px, but Star images are more that 1px.

Original issue reported on code.google.com by ashteroi...@gmail.com on 6 Apr 2012 at 7:33

GoogleCodeExporter commented 9 years ago 
On many occasions when I try to select Sol, I get Sirius. THAT SIRIUS PROBLEM! 
HAR HAR HAR! It doesn't make me *frumple* so much that I want to *dance* but it 
does make me spit *fat* words.

Original comment by triva...@gmail.com on 6 Apr 2012 at 8:37

GoogleCodeExporter commented 9 years ago 
The new user-friendly starmap cursor will look for stars in a certain radius, 
and snap to the largest, not the closest to the cursor.

http://code.google.com/p/project6014/source/browse/trunk/sc2/src/uqm/planets/pst
armap.c#1463

So if you managed to put the cursor to the SW of Sol so that Sirius wasn't in 
that radius, you'd get it.  Or if you zoomed in.

But we should fix this by snapping to the closest, unless the bigger one is on 
the same pixel maybe?

Original comment by ejrh00@gmail.com on 7 Apr 2012 at 6:49