@boroda, have you considered having only one $TitleCase function instead of 4 versions?
One that can use any or all of the three parameters?
Maybe have it mandatory for the formula to always contain three comma's, where it is optional for the user to put parameters in any of the three positions?
So:
$TitleCase(mandatory,optional,optional,optional)
So a basic version would look like:
$TitleCase(<Title>,a an and,,)
and something like:
$TitleCase(<Title>,,&,)
would also work?
(pretty useless, but to show what I mean)
this is what i've tried to make initially. but it turned out that this is not supported by MB for custom functions. though, i'm sure, MB supports this
internally. at least .NET allows this style of coding. i can't make this without Steven's support. we've pm'ed each other about adding support for this style to MB, but i'm still waiting for his answer. at least the answer "i won't do this".
EDIT:sorry, i actually meant this style of code:
$TitleCase(<Title>)
$TitleCase(<Title>,text1)
$TitleCase(<Title>,text1,text2)
as for this style:
$TitleCase(mandatory,optional
,optional
,optional
)$TitleCase(<Title>,a an and
,,)$TitleCase(<Title>,,&
,)it should be very easy for Steven to add support for this. all custom function parameters have type "string". MB could just pass empty strings as literally empty strings to the plugin.