Zugg Software :: View topic

Posted: Tue Aug 23, 2011 3:04 am

#STYLE BigNBold size:18,bold,italic
#CW to BigNBold

Use the above with any font usually set to 10-12 point.

1. Its not applied to the timestamp field, causing text in the buffer to appear scrunched up and overlayed. You can see how text goes missing in this picture.

Maybe if the line height for the whole line was padded to be the maximum size of any style used on that line... it could fix itself on the fly.

2. Styles cannot be embedded into the <color> tag of MXP

3. A style with no defined color should not override color attributes already in place.
Neither those set by the end user nor those sent from the mud.
This could allow for multiple styles to be applied to one snippet with only the most recent changes to any given characteristic affected by a style showing.

Posted: Sun Sep 04, 2011 9:48 pm

1) This is normal. CMUD does not support changing font size within a single line using styles, sorry.

2) That is correct. You need to use the <style> tag and not the <color> tag. Like <style BigNBold>text</style>

3) Hmm, a style without any color shouldn't be changing the color. Or try using a color name of "default" and see if that helps

Posted: Mon Sep 05, 2011 4:08 am

Is there a workaround for 1?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Not really. The closest thing is the MXP font tag, and that's not really going to produce much different results.

Posted: Tue Sep 06, 2011 11:27 pm

Actually, the MXP font tag *should* try to change the line height, although it will still be in multiples of the normal height (like taking up two rows instead of one for example).

Posted: Wed Sep 07, 2011 12:31 am

I have no issue with it throwing in an extra row to preserve spacing but...

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

#SUB is a "live text" command. If you don't want any triggers matching on the modified text, you need to remove the checkmark next to Trigger on Trigger, and possibly lower the priority AND put the checkmark on Stop Further Processing.

Also, your sub is missing a closing curly brace. Mr. Green

Posted: Wed Sep 07, 2011 4:26 am

Ok, now that works rather nice... why don't styles do this as well though?

That was an editing error cause the greater/lesser than symbols get messed up on the XML tab.