mudlet-makers team mailing list archive

[Heiko <koehnheiko@xxxxxxxxxxxxxx>]

Tested your MUD a bit. The MUD does send GA events correctly and behaves 
normally from what I could see.
Turn on the "fix prompt on new line" option in settings. The time 
command behaves as it should when I tried it, but the output was 
different compared to your replay.
If the problem presists please let me know.

HeikoKoehn schrieb:
> The replay shows the problem nicely. I'll have to analyse your MUD in 
> more detail tomorrow.
> Everest schrieb:
>> Here's a replay. The response to saying 'time' should be immediate. The
>> HP Bar and saying 'time' are all results of my input and subsequently
>> show the reply. There was no lag during this.
>>
>> One of the replies is also cut short. You'll see it. Happens every once
>> in a while.
>>
>> And I'm playing UOSSMUD (uossmud.sandwich.net port 9000). Let me know if
>> another replay could help.
>>
>> ** Attachment added: "13-07-2009#19-11-23.dat"
>>    http://launchpadlibrarian.net/28989791/13-07-2009%2319-11-23.dat
>>
>>   
>
>

-- 
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: New

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)