Problems with setting the width on a gridviewcolumn on a specific computer

3 posts, 1 answers
  1. Helge
    Helge avatar
    2 posts
    Member since:
    Feb 2015

    Posted 10 Feb 2015 Link to this post

    We have a problem with our software on one of our customers computers. When we use the following code:
    <telerik:GridViewDataColumn Width="0.9*" HeaderCellStyle="{StaticResource GridViewHeaderCellStyle}" DataMemberBinding="{Binding Name}" Header="{Binding Path=AppString.Name, Source={StaticResource ResourceWrapper}}" />
    We get the following error message in the error handler:

    Argumenter: 0.9*;Telerik.Windows.Controls.GridViewLength

    Anyone knows why this is happening, and only on certain computers (discovered on PC so far)?
  2. Answer
    Stefan X1
    Stefan X1 avatar
    482 posts

    Posted 12 Feb 2015 Link to this post

    Hello Helge,

    Would it be possible to provide us with more detailed information about which version of Silverlight your client is using and which version of our binaries have you referenced in your project? Is it the latest version (2014 Q3)?

    Best Regards,

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. DevCraft R3 2016 release webinar banner
  4. Helge
    Helge avatar
    2 posts
    Member since:
    Feb 2015

    Posted 12 Feb 2015 in reply to Stefan X1 Link to this post

    I have just solved this 10 minutes ago. This problem occured when the culture setting on the computer didn't match the format settings (that was overrided by the user). In this case the cutlure was set to English (US) while all formatting was changed to Norwegian style. One important difference between English and Norwegian cultures is the numeric format. 1,234.56 (en-US) is 1 234,56 in (nb-NO). We set the current culture in our application based on which user is logged in, so we have to research this problem some more to avoid this error in the future. But, for now the case is solved.
Back to Top