AccessibleDescription problem ?

[Louis]

I'm facing a strange behavior with radcontrols in my forms.
Everytime i compile the property AccessibleDescription of each radcontrols on my form are set to 

global::MyNamespace.Properties.Resources_fr.MANIFESTE_MSGBOX_SAVE_OK_TITLE;

this resource does exist in the resource file but is not used in this form at all.

Even when i replace this with an empty string, as soon as i get into the designer area the properties are reset to this value ??

Any ideas of what that could be?

[Dimitar Kapitanov]

Hi Louis ,

Please open a support ticket and send us a sample application so that we could test locally and verify your case.

Greetings,
Dimitar Kapitanov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Louis]

I think i found the reason. Still cannot see why this was happening but here is what i found. You could try to reproduce it.

In my project properties resources files, one of the resource key defined (MANIFESTE_MSGBOX_SAVE_OK_TITLE) didn't have any value. It was in fact the only key without a value. entering a value in this key resolved the issue.

Now why does this key without value gets picked by telerik controls? Very strange.

[Dimitar Kapitanov]

Hello Louis ,
If you take a closer look at the AccessibleDescription you will notice that it is marked Localizable (Localizable(true) ), and its default value is set to an empty string - DefaultValue(""). Because of the localization the value is persisted in the resources of the form, and because the default value is empty string (which in your resources is filed under the MANIFESTE_MSGBOX_SAVE_OK_TITLE key) the serialization / de-serialization mechanism of .NET makes the strange decision.

All the best,
Dimitar Kapitanov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center