drinkypoo wrote:Default keys? Arrows to pan, and z/Z for zoom in/out respectively. Control-F or the slash (/) key should jump to the search box, and hitting enter should select the system whose name is currently there.
The Arrow keys is already used to move focus, so that is not really an option. ATM they are WASD...
drinkypoo wrote:I have to admit I didn't try the panning keys - could you please put them into the application's help? Every time I think about it I start to look for where I saved the keys, and then some Uln a*hole in a Dodo starts trying to tractor me into something, and I get distracted
sure, I'll put them in the readme file... eventually I'll add a tab to changes the keys...
drinkypoo wrote:I will say that vsmap inside vstrade is FAR slower than vsmap by itself. Just drawing the initial map on which all systems are shown takes what seems like forever. And I'm running this application on a Core Duo
(I am DISPLAYING it on a P3 850, but it's RUNNING on the core duo, same machine that's running vegastrike - the still fully up-to-date SVN. I just did a SVN update with no changes today.)
The fun thing is that it does check if objects is in view before drawing them (which the original didn't). I did change the drawing routine in the 0.2.0.3 version, I'll change it back, if you can see a difference between 0.2.0.2 and 0.2.0.3...
The map draws smooth on my machine, but, that's a quad core, running vista...
drinkypoo wrote:Could you please draw a shadow behind units selected in vsmap? It can be VERY hard to read the system names. It would be great to have a 50% alpha'd drop shadow wrapped 1 pixel around the text, ho ho, but I would definitely settle for black. And anyway the display is too slow right now as it is.
yerh, I can do that... It might make vegamap somewhat slower, but not by much
drinkypoo wrote:Maybe you could do some kind of occlusion test where things which won't really be visible aren't drawn? That way when there's like 200 systems stacked on top of one another in the fully zoomed out view, you would only have to display two or three of them? But I know you didn't write vsmap originally and this might be harder than it sounds...
It's a great idea, but, as you guessed I don't know how to do it...
But, I'll add it to my ToDo list, and try to read up on the subject, and make some improvements...
drinkypoo wrote:And it would be GREAT if you could replace the pulldown zoom control with a slider with the zoom level shown next to it, it would be a more logical control for zoom level (in keeping with other applications etc.) The numbers don't really explain much (they're logical, but still, to the average user?) and so I would go with "in" at one end of the gauge, and "out" at the other. I've also seen gauges which are labeled with images, for example a small picture and a bigger picture. But as we've discussed before, we like text.
well the down side of a slider is that there is a maximum and minimum... currently you can zoom in as much as you like... you wouldn't be able to that with a slider... But, I do agree that the numbers is not exactly telling, but I don't know how to change them for the better... I wanted to keep the range within five digs (for the most parts).
drinkypoo wrote:Maybe I'll start trying to think of what the icons should look like if you ever want to put them in
please do... and if you got some mad drawing skills, you're also welcome to create the icons yourself...
drinkypoo wrote:Sorry I haven't done the panning test, but I can tell you that ALL of vsmap is too slow!
I know It's not optimal... But, I know little of what to do about it...
But I'll try to create some logic that minimize that draw calls, as you suggested...
EDIT:
I profiled the 0.2.0.3 version, and It's indeed extremely slow...
I optimized It, the best I know. The next alpha should be faster then both the original and the previous versions of VSTrade.
I didn't do all the fancy code you suggested, yet... so with that done (some day), we might even hit something usable...