|
Burser Wanderer
Joined: 07 Feb 2001 Posts: 70 Location: United Kingdom
|
Posted: Sat Aug 10, 2002 3:53 am
Focusing and the Black Arts of Status Windows |
I have built myself a number of FIFO command stacks in zMUD out of the pre-defined stringList commands, a string list, some triggers and a piece of e-stickeyback plastic.
This works a treat.
What I want to do, however, is to output the current state of the stack to a Window, be that a Status window or a normal Window.
Currently, I only know how to display one status window at a time, and can not find a way to use another two, preferaby three seperate ones.
If you could help me at this point, I would bow down, accept you as my god and worship you till Elivs comes back.
Using the %expandList(@commandQueue, %cr) command, I can format the queue into a window friendly version. Great, thought he. I can use windows, not status windows!
Not so.
The code works a little like this:
1) Make alterations to the Queue
2) Pop the next command and execute it
3) Recalculate queue lenghts
4) Send #CLR to the three mini-output windows
5) Write the new stringList to the window in that annoying blue.
Great! Or at least it would be if it didn't leave the window focus in the NEW window, taking it away from me who is user. I'm typing away to a friend in a room, when all of a sudden I'm adding "een the latest sword?" to the command queue.
So, to recap:
For imortal praise:
How do I use many status windows?
For a big thanks:
How do I prevent my code focusing the window away from the main MUD window when it writes to it.
When all else fails - there is always running away to fall back on.
---> Burser |
|
|
|
Burser Wanderer
Joined: 07 Feb 2001 Posts: 70 Location: United Kingdom
|
Posted: Sat Aug 10, 2002 4:32 am |
Oh, and while I'm at it:
Is there a way to query an Alarm to see how long it has left? (#ALARM +n {})
When all else fails - there is always running away to fall back on.
---> Burser |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Sat Aug 10, 2002 7:21 am |
Sorry you can not query an alarm to find out when it expires.
Regettably you can only have 1 status window, so your use of child windows is the workaround. I am guessing that you use the focus character (':' by default) to send commands to these windows. That results in item 4 of your first post should be ":windowname:#CLR". For item 5 you should use the #WINDOW command, you can add color formatting to it through the %ansi function so it isn't that annoing blue.
I am very tempted to write a multiple status window plugin, but it is a very back burner thought in my head. Guess everyone will have to live with one until Zugg feels like breaking the limits he set for himself a long time ago when the status window was first created. |
|
|
|
Humpton Apprentice
Joined: 10 Oct 2000 Posts: 158 Location: Chicago, IL
|
Posted: Mon Aug 12, 2002 6:26 pm |
Actually, you can get a display of how long an #ALARM has. Just type #ALARM at the command line and it will show ALL currently patiently waiting alarms and how long til the fire. It also shows what will fire so it can get a bit crowded if you have busy alarms and a number of them.
Stay JOLLY!
H
___
Humpton lives like he types.... fast, and full of mistakes!
Core 2651: For those who prefer the future to the past. |
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|