mudlet-makers team mailing list archive

[Catharsis <stenten@xxxxxxxxx>]

The last line of the output is gagged if the output is the result of:
another player's tell, say, emote, or channel message, as well as the
last line of battle spam.

The things that aren't gagged and show normally are the output results
of anything that I enter, including all my tells/says/channel messages,
emotes, attacks, commands, etc.

Basically, it seems that the gag is only for output originating from
somewhere else (MUD or another player). My output shows normally. If I
sit back and watch (not inputting anything), the output will always be
one line behind real-time.

Hitting Enter makes everything show up normally as if it were never
gagged. Switching to another window and back again also fixes the
output.

There's nothing notable in the command line when I run Mudlet from the
terminal.

Running Mudlet Beta 14 in Ubuntu 9.04.

If there's any other information I can provide, please let me know. I'm
at a loss for what else I can do to help.

-- 
Final line in output not displayed.
https://bugs.launchpad.net/bugs/395890
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: Incomplete

Bug description:
In the output, the last line, i.e. the last string of text sent from the MUD, isn't displayed. If a new string is sent to the output from the MUD, it causes the first to appear normally. It's like the output is always one line behind real-time.

This is only with MUD-side text though. Any output resulting from a command I enter is displayed normally. Entering a command or even a blank line fixes the output.

I'm running Mudlet Beta 12b, compiled from source in Ubuntu 9.04. 

Since I start Mudlet from the terminal, I can see odd strings it spits out. I think this one is relevant to this bug:
pE rect: QRect(0,0 1003x608)