Zugg Software :: View topic

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I have tried a number of methods to use color, but now it seems that I must use MXP if I am to duplicate the BG I chose. Could anyone tell me how to structure the MXP for the 2 db calls below. There are 4 db calls really as it is a conditional, but I don't know if I can just use one MXP statement, or much about modes and expansion here.

ty

#if (@totalspell_h > 0) {

Enchanter Joined: 09 Sep 2007 Posts: 605

Are you sure you need the #MXP? May be you'll start with something simple like #PRINT (or #SHOW)? All what I see in your sample code is plain text output.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

thanks for the help, you are very kind

(btw that is sarcasm)

Posted: Tue Mar 24, 2009 10:26 pm

No need for sarcasm. Actually, I believe he's correct. Why not do something like this.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

Your answer Tech was very apt, as I said I had tried a number of methods, and asked what would work. Trying show may work as your example differs from that I had used, and now I see that I wasn't taking the help file literally.

I would have accepted the first without sarcasm except since the code I displayed 'would' need to be expanded, how could I consider it text? Then I felt just %proper() was a leading function. Anyway.

I feel your example will fix my problem.

I would be happy to post the context of what I had with it's error, though just to accommodate after the fact.

And I apologize for assuming it must require MXP. I don't have a standard background color and that is difficult to work with but appealing otherwise. Nothing I have done was working. I had tried the obvious, however badly. Sorry, really.

This failed in v3.05:

Posted: Wed Mar 25, 2009 6:50 am

Hi Letitia,

I thought about this some more. Why don't you just set the window styles to have the background color you want instead of setting the background on the text you output?

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I changed the session window background to $1E2510 because I felt the default gray on black had an almost sharp contrast that could be improved.

Now when I change the foreground with a color, CMud does not recognize the new background, the results are a voided looking band that commands undesired attention. I wanted to make my own table of colors but have had only a little success.

http://home.comcast.net/~shibeka/CmudScreen.jpg

I like this olive BG as it is darker then the presets. Is there another way to avoid the black bands?

The color scheme here is off and designed for 'green hi' or 'chartuse' in ZMud.

As an aside, I just noticed my on-button color changed too since I used the beta yesterday morning. It may not be the beta though I think so at this point.

Wizard Joined: 22 Mar 2007 Posts: 2320

How exactly were you displaying the text that ended up in black bands?
It could be a Cmud bug, or it could be a problem in your code.
If you are simply defining a foreground color, the background color should not be changing.
So it may be more useful to track down this problem than play with resetting the background color yourself.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I'm not simply setting a foreground color, but a foreground on a background chosen from the 'pick other colors scheme'. I suppose you know this, so I will look for a problem.

entered on the command line:

Posted: Wed Mar 25, 2009 5:26 pm

Ok.. i see what you mean. I would argue this is a bug in the #COLOR command because it's not respecting the chosen background color. If you were to do

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

#PRINT prints. :D

I get an error with

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

Perhaps mine toggled something when the previous use of color failed, though I will reload the XML and then try the experiment from a blank session.

I am going with PRINT regardless

Posted: Wed Mar 25, 2009 6:05 pm

Not sure what you mean... #PRINT works just fine for me. If you are using 3.05 make sure you have force Remote MXP enabled.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

That test:

Posted: Wed Mar 25, 2009 10:07 pm

That's why it's important to post your version as well.

#SHOW treats test as if it came directly from the MUD. And Force Remote MXP says you'll allow MXP commands/tags from the MUD. So this option needs to be set for it work with #SHOW.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

Neat, TY