mudlet-makers team mailing list archive

[Everest <stenaglia2003@xxxxxxxxx>]

I bold the 'say' command, so that's probably why it looked differently.

Enabled "Fix new text to be on its own line" in Settings->Main Display.
Didn't notice any change at all, even after restarting Ubuntu.

Thinking it might be an Ubuntu problem, I installed Mudlet Beta 13 on my
Windows XP Pro SP3 partition. My computer shipped with SP1, so all the
hardware should be fully supported, and I've never had a problem with
it.

Bug is exactly the same in XP, with or without "Fix new text to be on
its own line".

This makes me think it has to be a hardware compatibility problem,
right? Since that's the only thing the two partitions have in common.
I've attached the output of 'lspci' if it'll be any help.

** Attachment added: "lspci"
   http://launchpadlibrarian.net/29025678/lspci

-- 
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)