Don't notify after clicking yes and localization

[Sébastien]

Hello,

1- If the user select "yes" to rate the app, why the control is asking it again?

2- Where do I localize this string by example MBYesText ? I tried to put it in my Strings.resx, but it didn't work.

Thank you
ArchieCoder

[Todor]

Hello,

Thank you for your questions.

1 - Selecting yes doesn't automatically mean that the app is actually rated and this is why the reminder keeps showing. However, we have recently added a new property called SkipFurtherRemindersOnYesPressed. If you set it to true, the reminders will stop after the user selects yes. In order to get the updated version of our controls with this property included, you can download our Latest Internal Build from your account.

2 - Our online documentation contains explanations on possible ways to localize your application. You can read more here.

Let us know if you need further assistance.

Greetings,
Todor
the Telerik team

[Sébastien]

Hello,

Thanks for the fast answers.

1- Can we publish an app using the latest internal build? Or when is the next plan release?

2- These steps from http://www.telerik.com/help/windows-phone/localization-string-loaders.html are confusing me :

InputLocalizationManager.Instance.StringLoader = new MyInputStringLoader();
LocalizationManager.GlobalStringLoad = new MyInputstringLoader();

InputLocalizationManager.Instance.StringLoader = null;

We create an object and set it and 2 lines after we put it to null! I need an explanation please :)

Thanks
ArchieCoder

[Todor]

Hello Sebastian,

1 - Yes, you can. However, you should have in mind that the internal builds that we release are not as thoroughly tested as our official releases, so you should pay more attention when publishing app with these assemblies. As to the next release, it will be Q1 2013 SP1, expected in early April.

2 - I agree that the documentation is confusing. What we had in mind is that you have two options for using string loaders. The first one is setting the string loader to the InputLocalizationManager's string loaded and the second one is setting it to the global string loader. When using the second approach, you need to make sure that the assemblies that are expected to use the global string loader don't have their own string loaders and this can be achieved by setting their string loader to null. In short, first approach:

InputLocalizationManager.Instance.StringLoader = new MyInputStringLoader();

Second approach:

LocalizationManager.GlobalStringLoader = new MyInputStringLoader();
InputLocalizationManager.Instance.StringLoader = null;

We are going to update the article in order to make it more clear.

Kind regards,
Todor
the Telerik team

[Sébastien]

Thanks, I'll look forward to the next release.