Hi,
A fix for this bug: https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1418043&group_id=119783
by adding a method like this:
protected boolean localizeDisplayValues()
{
return true;
}
to AbstractChoice so that users can override it and disable the localization of options.
But i am thinking about doing it in reverse. If you want localization you have to override it and return true
So by default i would return false;
I think there are many more selects generated that don't use localizations then there are that do..
And it does cost quite some perfomance, there is some string concatting and if the value is not found
it is currently constantly searched for.
That last part i think i can optimize
Localizer.getCachedValue
() shouldn't do this:
if (value == NULL)
{
value = null;
}
i think it just should return that NULL value and the 2 methods calling it should handle that
(by not searching for they key again)
johan
