https://github.com/Chris7/Mudlet2/commit/90830302b4548f83db742e83b7630e33e61d0fa6
** 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/1119774
Tit
https://github.com/Chris7/Mudlet2/tree/tempTriggers
--
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
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 me
We could use this branch to add trigger priorities for tempTriggers
efficiently, but this branch clearly needs extensive testing before we
can merge it.
Am 11.03.2013 21:07, schrieb Chris:
> Tested briefly, works.
>
> https://github.com/Chris7/Mudlet2/commit/f721b21fb086873611fab163ef44d001d192
Put this in a seperate branch plz to not make your repo incompatible.
Am 11.03.2013 21:07, schrieb Chris:
> Tested briefly, works.
>
> https://github.com/Chris7/Mudlet2/commit/f721b21fb086873611fab163ef44d001d1922e72
>
> ** Changed in: mudlet
> Status: Confirmed => Fix Committed
>
--
You
All we need is a few lines of code to rearrange the temp trigs at the
end of the trig root node after package import.
Am 11.03.2013 21:07, schrieb Chris:
> Tested briefly, works.
>
> https://github.com/Chris7/Mudlet2/commit/f721b21fb086873611fab163ef44d001d1922e72
>
> ** Changed in: mudlet
>
6 matches
Mail list logo
