 |
Castiel Newbie
Joined: 12 Mar 2012 Posts: 1
|
Posted: Mon Mar 12, 2012 6:40 pm
2 Question about windows |
1- I would like to have an information window in which all the echos should be showed from multiple sessions. When i try to do that each session opens its own info window? Could somebody plz tell me how can i fix that?
2-I also tried to use status window it kinda worked but seems like each command or text entered shows up extra status line in the package editor. how can i clear the contents of a status window Is there a way to do it from command line like #clr command.?
3-How can i delete triggers from command line or using other triggers? |
|
|
 |
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Mon Mar 12, 2012 10:07 pm |
1)I don't multiplay within the same instance of CMud. Aardwolf doesn't allow multiplaying except in the case when you connect to both the live and test server, but I take it a step further by not allowing one session any access to the other (in case I introduce a side effect or bug.)
2)The #STATUS or #STWIN command (re)defines a status object (status bar and status window, respectively), and they will show all the status objects that the current window can see (for example, your second session window cannot see any status objects contained in Session1's window object). Typically, you create the status objects via the Package Editor via script creation. The scripts would then just capture information to their respective variables, and the status object would then update accordingly with no other work necessary from the user.
3)normally, you don't want to create and delete stuff as this will slow down your scripting. You want to enable/disable via #T+ and #T-. Deletion of settings is done via the #UNsetting commands (#UNTRIGGER, #UNALIAS, etc), though. |
|
_________________ EDIT: I didn't like my old signature |
|
|
 |
Rahab Wizard
Joined: 22 Mar 2007 Posts: 2320
|
Posted: Mon Mar 12, 2012 10:59 pm |
1) How do you have your status window set up? I believe that you need to have the window in a separate package, and make sure each of your session modules are granted access to that window. Otherwise, when the different sessons try to send text to the window, they don't know it exists and they try to create a new one they can access.
|
|
|
 |
|
|