Bug Report T320258
Visible to All Users

Localization - Mask properties are serialized and added to the RESX file

created 9 years ago

I found a not expected behavior in the localization mechanism.

For clarity, I will try to explain the problem with an example:

  1. I insert a TextEdit in a blank form
  2. Set Localizable form property to true
  3. Change the language form property to English (our default locale is Italian)
  4. Save
  5. Change the language form property to default
  6. Now in the en resx there are some properties of the TextEdit mask (but I didn’t  make changes at mask in English). This is the unwanted behaviour.
  7. Set the mask of TexEdit to “Numeric n2” and UseMaskAsDisplayFormat to true
  8. I run the application in English and the Numeric mask is not active, running the app in Italian changes made to mask take effect

The problem is that I have different behavior for each language but mask and UseMaskAsDisplayFormat should not persist in english resx, since I need them to be language independent.

Suppose to change UseMaskAsDisplayFormat before changing Language property, I have same behavior for English and Italian.
When I Just switch language to English and back to default (Italian) from there I get a separate way behavior.
This does not happen with native windows forms controls.

Thanks
Roberto

Show previous comments (2)
Sasha (DevExpress Support) 9 years ago

    Hello Robert,
    What about UseMaskAsDisplayFormat property which is described in the ticket also?
    You can also make it non-localizable in a similar manner:

    Visual Basic
    <Localizable(false)> _ Public Overrides Property UseMaskAsDisplayFormat As Boolean Get Return MyBase.UseMaskAsDisplayFormat End Get Set MyBase.UseMaskAsDisplayFormat = value End Set End Property

    There are many other mask properties that have the same problem, for example: AutoComplete, BeepOnError, MaskType …
    The same goes for many properties of Appearance object, for example: SimpleButton.Appearance.Image and NavBargroup.Appearance.Image
    And also Properties.AccessibleName, Properties.AccessibleDescription,…

    I see this behavior. However, as I stated earlier, we use the standard DefaultValue attribute. We will research ways to improve this behavior and let you know our results.

      Hi Sasha,
      did you find a solution for this issue?
      Please let us know, thank you.

      Sasha (DevExpress Support) 9 years ago

        Hello Paolo,
        Our developers are researching this behavior. We will update this thread as soon as we make any progress.

        Answers approved by DevExpress Support

        created 6 years ago

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.