← Back to team overview

mudlet-makers team mailing list archive

[Bug 1132260] Re: Perm triggers created after temp triggers run after temp triggers

 

I was thinking about that but I didn't want to incur the speed hit of
going through the list twice, looking for non-temp first then temp
second.  Is it better for you to get a branch off the SF branch point or
just from my latest commits?

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

Title:
  Perm triggers created after temp triggers run after temp triggers

Status in Mudlet the MUD client:
  Fix Committed

Bug description:
  Temp triggers normally run after perm triggers, however but not if the
  perm trigger was created later. For example, when you reinstall a
  package or a module, its perm triggers will be running after existing
  temp triggers.

  This creates an issue where perm triggers rely on the original MUD
  colors to do their work, which temp triggers later modify. If those
  perm triggers start running after temp triggers, they won't work.

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


References