Menu Columns
Moderator: Forum Moderators
Forum rules
- Please use [code] BBCode tags in your posts for embedding WML snippets.
- To keep your code readable so that others can easily help you, make sure to indent it following our conventions.
-
Ken_Oh
- Moderator Emeritus
- Posts: 2178
- Joined: February 6th, 2006, 4:03 am
- Location: Baltimore, Maryland, USA
Menu Columns
FYI, the fix to Pango with menu images works. Thanks!
Now, I've noticed something else.
In [option] I used to be able to put = in somewhere to make another column, like so:
message="&"+attacks/something.png+"="+_ "description"="$cost"
Instead, now it shows that = sign and doesn't put the rightmost value in a separate column, I've tried removing the = and using the Pango markup gravity='east' but that didn't change anything.
Is there some new syntax for that now?
Now, I've noticed something else.
In [option] I used to be able to put = in somewhere to make another column, like so:
message="&"+attacks/something.png+"="+_ "description"="$cost"
Instead, now it shows that = sign and doesn't put the rightmost value in a separate column, I've tried removing the = and using the Pango markup gravity='east' but that didn't change anything.
Is there some new syntax for that now?
-
SkeletonCrew
- Inactive Developer
- Posts: 787
- Joined: March 31st, 2006, 6:55 am
-
Ken_Oh
- Moderator Emeritus
- Posts: 2178
- Joined: February 6th, 2006, 4:03 am
- Location: Baltimore, Maryland, USA
Re: Menu Columns
Great, thanks. I guess I should check the bugs.wesnoth more. Another thing I noted is that & within text breaks the markup (or maybe that's been noted in bugs...). I guess I should probably help you guys out by doing a full test on all of the characters but I'm pretty engrossed with what I'm doing atm.