 |
Bremen
Novice
Joined: 26 Dec 2002
Posts: 33
Location: USA
|
 Posted: Fri Oct 07, 2005 4:11 am
#FORALL #SAY blank line after 2
|
I noticed this in 7.05 when I first wrote a sorting script, and it's still present in 7.13, I assume it exists in 7.21.
1) I capture lines of output into a string-list variable (or parts of the output).
2) I sort the variable
3) Using #FORALL @variable, I #SAY the data (with some formatting)
4) Regardless of computer speed/etc, it will #SAY the first 2, pause exactly long enough to display my prompt from the MUD, and then #SAY the rest.
Example:
You are affected by the following:
Skill: blackrose (05:48)
Skill: sneak (00:54)
Spell: infravision (03:27:19)
Spell: combat mind (01:00:15)
Spell: giant strength (56:30)
Spell: darkness (03:13)
You are affected by 2 skills and 4 spells. <-- this is where I %sort() and begin the #FORALL
Spell: 207 min infravision
Spell: 60 min combat mind
1662hp..blahblahprompt
Spell: 56 min giant strength
Skill: 5 min blackrose
Spell: 3 min darkness
Skill: 0 min sneak
Is there a reason this happens or anything I can do to avoid it? It looks really ugly, is it just a bug in how zmud handles things? Note that there is some %ansi processing in the #SAY's, so it's not easy to whip up something to reproduce it. I can't remember right now if the pause only happens when the #FORALL is running directly after a %sort(), I'll have to test that tomorrow. |
|
_________________
--Bremen, zMUD 7.21 on Windows 7 x64 |
 |
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Fri Oct 07, 2005 7:35 am
|
Put the #FORALL into a #PRIORITY command.
| Code: |
#PRIORITY {
#FORALL {
#SAY {blah}
}
} |
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Bremen
Novice
Joined: 26 Dec 2002
Posts: 33
Location: USA
|
Posted: Fri Oct 07, 2005 3:27 pm
|
Perfect, thanks!
|
|
|
|
|
|
|
|
