This is a migrated thread and some comments may be shown as answers.

Windows7 Theme doesn't seem to work anymore with latest internal build

9 Answers 64 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Licenses
Top achievements
Rank 1
Licenses asked on 07 Jun 2011, 10:33 AM
Hello

Today I upgraded from Q1 SP1 to the latest internal build (RadControls_for_Silverlight_4_2011_1_0606_DEV_hotfix.zip). This because of another bug that is now fixed.

However, this upgrade seems to have broken the Windows7 theme, since all our radbuttons, radcomboboxes, raddatepickers,... etc are now gray instead of the Windows7 blue.

We don't do anything fancy to apply the theme. Just a reference to the Telerik.Windows.Themes.Windows7 dll and this line in the resourcedictionary in the app.xaml.
<telerik:Windows7Theme x:Key="TelerikTheme" IsApplicationTheme="True" />

This has always worked until the upgrade to the latest internal build.

9 Answers, 1 is accepted

Sort by
0
Licenses
Top achievements
Rank 1
answered on 08 Jun 2011, 08:15 AM
I also tried to set the theme in the code-behind instead, as instructed by http://www.telerik.com/help/silverlight/common-styling-apperance-setting-theme.html

        public App()
        {
            this.Startup += this.Application_Startup;
            this.Exit += this.Application_Exit;
            this.UnhandledException += this.Application_UnhandledException;
 
            StyleManager.ApplicationTheme = new Windows7Theme();
 
            InitializeComponent();
        }

Without success... The buttons and input controls (datepicker, combobox, ...) are still gray.
0
Valeri Hristov
Telerik team
answered on 08 Jun 2011, 11:08 AM
Hello,

I was able to reproduce the problem, we will do our best to fix it for the internal build next week.

Regards,
Valeri Hristov
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Licenses
Top achievements
Rank 1
answered on 14 Jun 2011, 08:19 AM
Ok, thank you.

Could you please notify me when this problem is fixed? I've subscribed to this thread, so just leaving a post here will do.

We really need this, because the nightly build fixes the annoying problem where a gridview bound to a QueryableDomainServiceCollectionView occasionaly causes an IndexOutOfRangeException while reloading (my support ticket 414382).

Thanks!
0
Valeri Hristov
Telerik team
answered on 14 Jun 2011, 11:36 AM
Hello,

Today we released a new internal build that should solve the problem with the Windows7 theme from the last week.

All the best,
Valeri Hristov
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Licenses
Top achievements
Rank 1
answered on 14 Jun 2011, 11:38 AM
Ok, thank you.

I'll try it right away.
0
Licenses
Top achievements
Rank 1
answered on 15 Jun 2011, 10:10 AM
The latest build fixed the Windows7 theme problem.
 
Sadly it introduces a new problem...

We do have a lot of radgridviews in our application. Some of them are in a detail form. We have not set a fixed width, so they size nicely depending on the data contained in it. Well, at least that's what they used to do...
 
In the latest build these gridviews get stretched horizontally beyond control. When you start scrolling, they sometimes even contain holes.

The problem only seems to occur for gridviews within a ScrollViewer. We try to avoid putting gridviews in a scrollviewer, but in a detail form, containing other data as well, that is not an option in most cases.
0
Yordanka
Telerik team
answered on 16 Jun 2011, 08:54 AM
Hi Sodi We,

Placing RadGridView in a ScrollViewer is not recommended and may cause unexpected results as those mentioned by you. In case you don't want to replace the ScrollViewer with another element, as a possible solution you may set fixed sizes for the grid.
 
Greetings,
Yordanka
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Licenses
Top achievements
Rank 1
answered on 16 Jun 2011, 01:16 PM

I know RadGridViews perform the best outside a scrollviewer (eg. for row/column virtualization), but since these grids contain a limited number of rows, this is not an issue.

However, the scrollviewer doesn't seem to be the cause of the issue, it merely blows it up beyond control. The issue is there without a ScrollViewer as well.

You can see the difference while building a very simple sample with Q1SP1 and the latest internal build. You should do nothing more than placing a RadGridView in Grid with a Column having a width of "Auto".

In the previous versions of the controls (eg Q1SP1), the gridview nicely fits to it's contents.
In the latest internal build, the gridview stretches horizontally to fill the entire screen (with a scrollviewer it stretches over like 100 screens).

   <Grid x:Name="LayoutRoot" Background="White">
 
            <Grid.ColumnDefinitions>
                <ColumnDefinition Width="Auto"/>
            </Grid.ColumnDefinitions>
  <telerik:RadGridView x:Name="documentList1" ItemsSource="{Binding DocumentListItems, Mode=TwoWay}" ValidatesOnDataErrors="InEditMode" AutoGenerateColumns="False" >
                    <telerik:RadGridView.Columns>
                        <telerik:GridViewDataColumn Header="Name" DataMemberBinding="{Binding ClientDocument.Name, Mode=TwoWay, NotifyOnValidationError=True, ValidatesOnNotifyDataErrors=True, ValidatesOnDataErrors=True, ValidatesOnExceptions=True}"  Width="Auto" IsReadOnly="False" />
                    </telerik:RadGridView.Columns>
                </telerik:RadGridView>
</Grid>


0
Yordanka
Telerik team
answered on 17 Jun 2011, 03:31 PM
Hi Sodi We,

The issue has been fixed and the fix will be part of the next internal build on Monday.

Excuse us for the inconvenience caused.
 
Greetings,
Yordanka
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Tags
General Discussions
Asked by
Licenses
Top achievements
Rank 1
Answers by
Licenses
Top achievements
Rank 1
Valeri Hristov
Telerik team
Yordanka
Telerik team
Share this question
or