phillszymanski / nethack-android

Automatically exported from code.google.com/p/nethack-android
0 stars 0 forks source link

Revision of the two message bars #64

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
There's a few things I don't like about the message bars in this port.  For 
one, these message bars contain 90% of the game's content. I feel they deserve 
a bit more real estate than they have been given. 

Top message bar: 
1. This bar deserves space for at LEAST 3 physical lines. 
2. Don't clear the text each action. The last message you get should be at the 
top of the screen all the time. It gets annoying to be walking along, a message 
pops up, then disappears because you take another step, thus forcing you to ^P 
to see the log.
3. Get rid of --more--.  That constant pausing really screws with the flow of 
the game.  With #1 and #2 implemented, the chances of you missing important 
messages are minimal, and if you see a bunch of text scroll off the screen, 
that's what the full log is for.
4. Related to #3 in that it disrupts the flow of the game, get rid of the full 
screen item list popups when you walk over a spot with 4-5 items. I like that 
the top message bar will list the items if there are only a few, and if it's 
alot it says "Many items" and so forth. It's the in-between amounts where it 
gives you a full screen popup that becomes annoying. Just stick with the 
message bar, and if it doesn't fit, revert to "Many Items..."

Bottom Bar:
1. Too much information is crammed into two lines, especially the second line. 
The most important information (burdened, confused, stun, satiated, hungry, 
etc) always gets placed at the end of line 2. Starting around mid-game, your 
dungeon level, gold, hp, power, AC, and level all start growing to the 
double/triple/quadruple digits, slowly pushing that important information off 
the side of the screen until you can't see it anymore.  This lack of space also 
makes it nearly impossible to use any of the extra info options like displaying 
time (ticks) or exp.

Original issue reported on code.google.com by Deleriu...@gmail.com on 5 Dec 2010 at 8:34

GoogleCodeExporter commented 8 years ago
This should be the highest priority concern imo.

Original comment by b0llw33...@gmail.com on 27 Feb 2013 at 3:24