Kill count screen cuts off on long-named monsters

[narc0tiq]

Example:

The monster's name being shown in the example is giant black widow spiderling, and as far as I can tell, it probably printed the count (in this case, 5) on the next line, where it got overwritten by the 2 from the giant wasp kills.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[illi-kun]

Changing the number of records per line from 3 to 2 should help (it can be done in the file game.cpp, function void game::disp_kills()).

[narc0tiq]

Seems to me like that'd lead to a lot of whitespace hanging around -- there's already a fair bit of it visible in the above screenshot, making it all the more "interesting" to try to tell which number goes with which name. Clipping the name or letting an entry use more than one row seem like better options.

There's also the Dwarf Fortress option of cutting letters out of the middle of words to make them fit in limited horizontal space ("gnt blk wdw spdrling" would fit), and might be usable in other places, as well -- but I can't imagine how that would interact with localizations. Probably poorly.

[BevapDin]

@narc0tiq How about given every second row a different background color? Would this solve the two much whitespace problem and allow 2 columns? Github does it:

aaa	bbb	ccc
aaa	bbb	ccc
aaa	bbb	ccc
aaa	bbb	ccc
aaa	bbb	ccc
aaa	bbb	ccc
aaa	bbb	ccc

[KA101]

Sounds like a great idea, until we can't always guarantee contrast. Grey critter shows up on grey line, illegibility ensues. :-/

[narc0tiq]

@BevapDin That might be okay if we don't color the critter name, otherwise we run into the problem @KA101 just mentioned.

It'd also make it a lot easier to follow which number goes with which critter, and that can only be a good thing.

[KA101]

Obvious solution is to then lock all names into contrasting colors with their lines. Seems worth a shot.

[kevingranade]

What about alternating bold and non-bold?

[KA101]

That would work too.