mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Public bug reported:

Newly-created looping aliases get their content erased - see attached
video demo.

Introduced by
https://github.com/Mudlet/Mudlet/commit/b925a00e537f675da4a0b3681968128577739cbd,
I suspect the issue lies in returning out of the function so early - the
function might be doing additional setup later on.

One idea is to instead self-disable the alias. Then it'll keep self-
disabling and stay disabled until the looping condition doesn't match
anymore.

As to whenever should it self-enable after the looping condition is
fixed, I'm not sure yet.

** Affects: mudlet
     Importance: Undecided
         Status: New

** Attachment added: "Newly-created, looping aliases get wiped.mp4"
   https://bugs.launchpad.net/bugs/1268114/+attachment/3946072/+files/Newly-created%2C%20looping%20aliases%20get%20wiped.mp4

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

Title:
  Newly-created looping aliases get their content erased

Status in Mudlet the MUD client:
  New

Bug description:
  Newly-created looping aliases get their content erased - see attached
  video demo.

  Introduced by
  https://github.com/Mudlet/Mudlet/commit/b925a00e537f675da4a0b3681968128577739cbd,
  I suspect the issue lies in returning out of the function so early -
  the function might be doing additional setup later on.

  One idea is to instead self-disable the alias. Then it'll keep self-
  disabling and stay disabled until the looping condition doesn't match
  anymore.

  As to whenever should it self-enable after the looping condition is
  fixed, I'm not sure yet.

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