Provided that the intent is to associate a string (
const char *
) with a particular dialog type, an implementation like this one could be used.
template<class Ty>
struct CVHDialogTmpl
{
CVHDialogTmpl()
{
}
INT_PTR DoModal()
{
return t.DoModal(ptr);
}
Ty t;
static const char * const ptr;
};
template <class Ty>
const char * const CVHDialogTmpl<Ty>::ptr = "Generic text";
struct A { };
struct B { };
struct C { };
const char * const CVHDialogTmpl<A>::ptr = "Text for A";
const char * const CVHDialogTmpl<B>::ptr = "Text for B";
A possible variation to allow custom text to be used would be to make the following changes:
template<class Ty>
struct CVHDialogTmpl
{
CVHDialogTmpl() : actualText(ptr)
{
}
CVHDialogTmpl(const char *customText) : actualText(customText)
{
}
INT_PTR DoModal()
{
return t.DoModal(actualText);
}
Ty t;
const char *actualText;
static const char * const ptr;
};
In practice, that final solution is far better if there might be a situation where the text might sometimes differ. Assuming that the text is a filename for the dialog template, then most of the time the template associated to that type would be used but if in some situation a different template should be used then the constructor with one argument could be used.
By using a function and
typeid
/
typeinfo
, this solution could easily be extended to provide a text that depends on the type, thus if some convention are followed like the filename should be the struct/class name without the leading capital letter if it is C and followed by another capital letter, it would be possible to not specify it explicitly for that type. This would be compiler specific as the returned name might vary... In that case, the actual text to use might be stored in a
std::string
.