limit length of name

0 views
Skip to first unread message

Lord Kronos

unread,
Aug 24, 2008, 4:20:00 PM8/24/08
to mysqlgame
Would it be possible to limit the length of the name (or at least how
many chars are displayed). I've found a few instances where people
have very long names, which makes that column very large. Ex: shard 1,
row 604

Alex Rubin

unread,
Aug 24, 2008, 8:20:11 PM8/24/08
to mysqlgame
I'll look into a possible fix for this.

lolzj

unread,
Aug 25, 2008, 9:05:47 AM8/25/08
to mysqlgame
..Yes, I'm very close to 604, drives me absolutely insane. Hopefully
you guys figure something out soon. :/

Lord Kronos

unread,
Aug 25, 2008, 11:50:02 AM8/25/08
to mysqlgame
As an alternative, would it be possible to just move the name/owner to
the end of the row? Myself, I really couldn't give a care who the
person I'm attacking is. I really just want to see the row number, and
the relevant stats (money, fuel, attackers, defenders, and
multipliers). The only thing then is you'd probably want to highlight
some of the rows in a different color to indicate allies in your
clique.

mysq...@gmail.com

unread,
Aug 25, 2008, 2:58:35 PM8/25/08
to mysqlgame
OK, if you refresh dashboard, names in browse should now be limited in
width, with full name as hover text. I also added a name limit of 20
characters, which should have been there from the start.

On Aug 24, 4:20 pm, Lord Kronos <ldkro...@gmail.com> wrote:

lolzj

unread,
Aug 25, 2008, 4:20:42 PM8/25/08
to mysqlgame

Thank you! Much better. :)

Warll

unread,
Aug 25, 2008, 4:34:41 PM8/25/08
to mysqlgame
Won't this be a problem for the cliques?

Lord Kronos

unread,
Aug 25, 2008, 7:01:40 PM8/25/08
to mysqlgame
Oh, so much better. Thanks.


> Won't this be a problem for the cliques?

Yeah, that's why my followup suggestion of coloring the rows of your
clique members (just like your own rows are green) would be a good
idea.

mysq...@gmail.com

unread,
Aug 25, 2008, 8:18:29 PM8/25/08
to mysqlgame
Believe it or not that feature is sitting behind comments -- we pulled
it to save on the lookup, and it didn't seem important enough to
cache, so we'll add it back in when we can.
Reply all
Reply to author
Forward
0 new messages