 |
Leitia
Adept
Joined: 04 May 2007
Posts: 292
Location: Boston
|
 Posted: Sat Mar 28, 2009 7:21 pm
Color Problems
|
As a work around to the voided backgrounds I tried to #EXEC an alias with the following inside a variable.
| Code: |
| %concat("<color ",%db(@AllPref,@curkol), " ",%db(@AllPref,col_bg), "> ", %params," </color>") |
#SH and #MXP treated this as text
#Print executed it in color and also treated it as text,
Currently my system is partially ignoring this trigger (only).
Simply using color names vice database keys doesn't help in the tests I did.
Thought it was weird that print behaved differently and might be significant.
These hangups make finding workarounds for an alternative color background too much work. I really love my color scheme, and hope this background thing might be an easy fix. |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Mar 30, 2009 1:58 pm
|
Could you show us your actual code? I'm not following exactly what you are trying to do here.
|
|
|
|
|
Leitia
Adept
Joined: 04 May 2007
Posts: 292
Location: Boston
|
Posted: Mon Mar 30, 2009 3:57 pm
|
Sorry, I made a mistake.
I can't just use #CO blue on a changed background (as it uses the black background then) and was thinking #COLOR and #PRINT differ in some significant way toward being able to use #CO blue eventually. That would be Zugg doesn't already know how to fix the black background thing, but he probably just has lots of other things to do.
I was trying to help with information, not really get help.
Anyway, I had been trying to use # instead of $ to declare a hex number background with #COLOR. I forgot because it was inside a database.
I am unsure why MXP failed after trying this, but want to guess. I guess that in ZMUD MXP coding set a variable with a #, and in CMUD #COLOR somehow sets or evaluates that MXP variable but with or for $.
I am speaking out of my thrifty but stylish hat. I know nothing about these things except using the $ reset my scheme and it is predictable again. As an aside, I did get a floating point error in the process.
Sorry for being obscure, but that is my M.O. |
|
|
|
|
|
|
|
|
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
|
|
