Quote from: Quentin Sculo on April 06, 2013, 21:58:35still no luck
I've just did a test and it works. Note that custom fields will always begin with an uppercase letter, to avoid clashes with possible future standard fields. And it is case sensitive, so you need to use exactly the word that appear in the column in the Fields tab.
custom fields tags "written"* by GMB are read. others are ignored.
Quotegood! dumb question: is this already implemented? if so, what's the syntax? thanks
In the SongInfo widget, by default it will only show the field if the current song has a value for it. You can also look at the info tab of a song properties dialog, there the field should appear even if empty.Quote- will markup support IF sentences with boolean operators?yes
Quotethank youQuote- would you provide an example of how to customize font and color with markup?The pango markup doc is there : https://developer.gnome.org/pango/unstable/PangoMarkupFormat.html
Example with a Test custom field : Text1(markup='<span foreground="blue" font="Arial 15">$Test</span>')
You have to pay attention to quotes, use one kind (single or double quotes) for the markup='...' and another for the span properties.
Quote???Quote- is, or will ever be, possible to use markup on a SongList column?I don't know
PS
* why isn't writing to TAG allowed? =/