Databases
StackOverflow2013
Postsdbo
POStyle WPF normal Control depending on Windows Theme
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStyle WPF normal Control depending on Windows Theme
    primarykey
    data
    text
    <p>I have read lots of thing about WPF Theme, Skin, Style etc... But there is still something I cannot achieve.</p> <p>I have custom controls, which are styled depending on the OS theme, by having a different style in each of the theme file (Aero.NormalColor.xaml, Luna.NormalColor.xaml or Aero2.NormalColor.xaml), this work like a charm.</p> <p>I don't load/force any theme in my App.xaml, each controls (like buttons) keep there style depending on the OS theme. So I see XP buttons on XP, Win7 buttons on windows 7 and Win8 buttons on Windows 8.</p> <p>I also have ResourceDictionaries which are loaded in the App.xaml that contains "named" (explicit x:Key) styles for different normal wpf controls. They look like this:</p> <pre><code>&lt;Style x:Key="BlackComboBox" TargetType="{x:Type ComboBox}"&gt;&lt;/Style&gt; </code></pre> <p>and I use them like this</p> <pre><code>&lt;ComboBox Style="{StaticResource BlackComboBox}"&gt;&lt;/ComboBox&gt; </code></pre> <p>So for now, my BlackComboBox is the same on every Windows (XP/7/8).</p> <p>What I try to achieve is to have a different Style for these normal Controls depending on the OS theme, without having to subclass the Control (I think it will be overkill to have a subclass for each control that will need an OS specific them), so BlackComboBox could be different on each OS. </p> <p>I have already tried to put a style with the same key in a theme file, but this doesn't seem to work.</p> <p>I have thought about loading at runtime a different ResourceDictionary containing the style for the desired OS version:</p> <ul> <li>But it looks like an ugly solution.</li> <li>I don't like having to check for System.Environment.OSVersion. </li> <li>And it will not be theme dependant, but OS dependent.</li> </ul> <p>For me the best way seems to be able to have "named" style in a Theme file that kind of overrides the one in the ResourceDictionaries.</p> <p>Thanks for the help!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USStrAbZ
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. USStrAbZ
      1. VTBountyStart
    2. VO
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you actually creating different Templates that you want to use for each theme or are your named Styles just setting simple properties (i.e. Background, BorderBrush, etc)?
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. USJohn Bowen
    2. COFor some of them it is just Style with brushes, but for the most part I also change the Template (inside the Style)
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. USStrAbZ
    3. COI know that Actipro's library has theming support for native controls for XP, Vista, 7, Office etc.. but they create SharedResourceKeys that are referenced like so in XAML styles: "{DynamicResource {x:Static themes:AssetResourceKeys.MenuItemBorderNormalBrushKey}}" And they have some sort of ResourceManager that controls it.
      singulars
      1. POStyle WPF normal Control depending on Windows Theme
      1. USAlan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload