mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #02303
[Bug 522935] Re: Mudlet shouldn't report a width > wrap settings
** Changed in: mudlet
Status: New => Fix Released
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/522935
Title:
Mudlet shouldn't report a width > wrap settings
Status in Mudlet the MUD client:
Fix Released
Bug description:
Mudlet appears to be using telnet (sub)negotiation to report to the
MUD server what the screen width of the visible client area is. That's
great, however, it's always sending the real width... which sounds
good, except! Its actually not the real width, as Mudlet's wrap width
is the /real/ maximum width of a line.
This is actually pretty bad, because some muds present UI's of
customizable widths according to these negotiated values (or values
set manually by players if they wish to override it). For example, if
you have a wide screen showing up a lot of fields, it might show you
four columns of items. But for someone with a smaller field, it might
just show you two. Or it might be drawing a box and using your max
screen real-estate. Sure, it could default to 80 and be old-school,
but.. the width negotiation makes it a lot more awesome :)
IMHO, the "correct" behavior is for Mudlet to simply report the
shortest of (current screen width, wrap width). I can't imagine any
situation where it would produce favorable results to report to the
mud a wider width then the wrap width.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/522935/+subscriptions
References