Default TTD string as substring?

Discussions about the technical aspects of graphics development, including NewGRF tools and utilities.

Moderator: Graphics Moderators

Post Reply
User avatar
andythenorth
Tycoon
Tycoon
Posts: 5658
Joined: 31 Mar 2007 14:23
Location: Lost in Music

Default TTD string as substring?

Post by andythenorth »

NML won't compile this: "Expected a (literal) string".
string(STR_EXTRA_TEXT_SECONDARY, string(STR_EXTRA_TEXT_SECONDARY_CARGO_SUBSTR_THREE_INPUTS, string(STR_EXTRA_TEXT_SECONDARY_CARGO_SUBSTR_DETAIL, TTD_STR_CARGO_SINGULAR_COAL, string(STR_EMPTY)), string(STR_EXTRA_TEXT_SECONDARY_CARGO_SUBSTR_DETAIL, TTD_STR_CARGO_SINGULAR_COAL, string(STR_EMPTY)), string(STR_EXTRA_TEXT_SECONDARY_CARGO_SUBSTR_DETAIL, TTD_STR_CARGO_SINGULAR_COAL, string(STR_EMPTY))), string(STR_EXTRA_FLOUR_MILL, string(STR_EXTRA_FLOUR_MILL_GRAIN_SUBSTR), string(STR_EMPTY)))
This is triggered by the substring use in:
STR_EXTRA_TEXT_SECONDARY_CARGO_SUBSTR_THREE_INPUTS :{STRING}{}{STRING}{}{STRING}{}
The compile succeeds if I swap 'TTD_STR_CARGO_SINGULAR_COAL' for something like 'string(STR_FOO)'.

Default TTD strings can't be used in substring substitutions? Or the syntax is wrong?

It's a pretty horrible stack of substrings eh, but will save translators a lot of time if it works :)
Post Reply

Return to “NewGRF Technical Discussions”

Who is online

Users browsing this forum: No registered users and 15 guests