Zugg Software :: View topic

Posted: Wed Aug 08, 2007 9:58 pm

Are #STWIN settings supposed to persist after closing the session? They didn't in zMUD.

In zMUD, to add to an existing #STWIN you had to use the + argument, or the old value was replaced with the new value.

In CMUD not using the + argument you get a bunch of nameless #STWINs that all appear in the order the were created.

#STWIN hi
#STWIN there
#STWIN + there

All do more or less the same thing

The differences are that when you use the + argument, the #STWIN is given a name (which allows for just updating it, if it was used before) as well as a value (name and value contain the same string), and the variables are not expanded in the setting itself (as they are without the + argument), but in the status window.

Posted: Thu Aug 09, 2007 12:43 am

In CMUD, the full correct syntax is:

#STWIN {text stuff here} "classname" "idname"

You need the {} around it for the variables to get stored properly. The weird + syntax from zMUD is no longer recommended (although it's still in the code for compatibility). Each #STWIN creates an additional status window item, unless you use the optional "idname" field to give it a name. If you use the "idname" argument, then the new definition will overwrite the previous definition.

When using the + syntax, there isn't any classname or idname arguments. Everything after the + is taken as the status definition.

And yes, status window items persist between sessions just like any other settings.

Posted: Thu Aug 09, 2007 2:40 am

Amazing how much CMUD makes me clean up my code, but thats a good thing.

Workin good now, but another issue ive noticed.

Refreshing the #STWIN with a trigger will pull CMUD to the front when you are in another program but does not actively take focus, only visually. Anyway we can get this 'feature' removed?

And is there a way to set how many seconds the lil side status window pops out for? As it is, it flickers into view and hides itself from no mouseOver almost instantly.

Posted: Thu Aug 09, 2007 5:03 pm

Can you give me a specific trigger example that is causing CMUD to come to the front? I haven't seen that myself. Also, what version of Windows are you using?

I've got some items on the wish-list for controlling the fly-out timing, but I haven't implemented them yet.

Posted: Thu Aug 09, 2007 9:49 pm

any trigger that redefines a #STWIN by name such as:

#STWIN {Forging Stats%cr<color red>Hour: @forgeHours</color>%cr<color blue>Best: @bestpiece</color>%cr<color orange>Norm: @normalPiece</color>%cr<color yellow>Ave : 1:%eval(@normalPiece/@bestpiece)</color>} "Forging" "ForgeStatus"

Yes, I realize that i dont have to reinput this everytime for the variables to update (though i think i read somewhere that i might if i am using a database variable) in the status window.

As for the versions i am using... take a look at my signature.