Comment 11 for bug 763567

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Astuur> Saving the position in the Ctrl+0 slot, to be able to go back. (roughly summarized)

There's a couple of problems with this approach. First off, the game should not overwrite if the player has already stored something in 0 already. The game should not change something the user has set without the user being aware it has happened. This is why for instance autosave uses it's own slot separate from the ones the user stores. The obvious counter would be to disable that slot for the player so that only the game is able to change it. While this is possible, I don't really see the need to in effect disable one slot to have it used for this purpose.

Secondly, when a player is closing the window, how is it logical to press 0 to go back to where (s)he was? Even after the player has been informed in some way, I'm not sure how obvious this is.

Venatrix > a button for going back to the starting location

I actually like this a bit better than close and go back.

However, when thinking about it I suddenly realized something in general about the "go-back-to-where-I-started"-approach. Say I open the messages in position A, read some, scroll a bit around on the map to point B which is close to my border and observe that section for a while. I receive some messages which I read, and then I want back to B which is where I was recently. Instead I will be brought back to A instead where the window was first opened. I know I for one like to keep some windows open as I move about on the map, without really remembering where they were opened.

Counter A: "have it timebased or something, so that if you move your vision it will update to that place rather than where you opened the window". I think this would be too imprecise and would create problems by guessing which area the player meant.
Counter B: "close and reopen messages" Would work, but it is sort of a strange requirement. Plus people will still leave their windows open.
Counter C: "have yet another button to set current position to the go back point" Would work, but fills the window with buttons :p plus it duplicates the CTRL+number slots already in existance.

So that's some arguments. Please let me know if I'm getting too negative commenting here... :)

I still think this problem is better handled by features already available:
1. It is possible to delay responding to messages. If my border is under attack and a mine runs out of resources I'll handle the mine when I have the time. My border is more important and more harm will happen if I leave that unattended than the mine.
2. Getting back to an area quickly. If the area is important, and you need to go back often, use CTRL+number, click on the minimap or scroll to the area. You may not back to exactly where you want as suggested here, but you should be close enough.