mudlet-makers team mailing list archive

[Ixokai <ixokai@xxxxxxxxx>]

Public bug reported:

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.

** Affects: mudlet
     Importance: Undecided
         Status: New

-- 
Mudlet shouldn't report a width > wrap settings
https://bugs.launchpad.net/bugs/522935
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: New

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.