mudlet-makers team mailing list archive

[Heiko <1117858@xxxxxxxxxxxxxxxxxx>]

that's clearly a bug. emit signalEchoMessage() is code from stone age :)
logError() should be used everywhere

Am 11.03.2013 01:09, schrieb Chris:
> It's because compileAndExcuteScript does this:
> emit signalEchoMessage( mHostID, QString( e.c_str() ) );
> instead of doing logError.
> compileScript doesn't use logError as well, not sure if it should or not.
>
> https://github.com/Chris7/Mudlet2/commit/19b3266fa6b2ad3b3ad06bc5f63285498c2ce6f5
>
> ** Changed in: mudlet
>         Status: New => Fix Committed
>

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1117858

Title:
  Syntax errors inside setLink code can get shown on the wrong profile

Status in Mudlet the MUD client:
  Fix Committed

Bug description:
  Syntax errors inside setLink code can get shown on the wrong profile.
  For example, I had 2 tabs open, and was working with setLink in one of
  them. When setLink code had a syntax error in it, nothing showed up in
  the errors view - however on the main screen of another, completely
  unrelated profile, the error messages were showing up in white.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1117858/+subscriptions