Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3428176
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T06:55:39+00:00 2026-05-18T06:55:39+00:00

Why doesn’t the following style work? I have in other places the exact same

  • 0

Why doesn’t the following style work? I have in other places the exact same construct with different controls and it works.

Using TargetType="{x:Type Separator}" instead of TargetType="Separator" doesn’t work either. Neither moving Style upper in the XAML hierarchy. Can I avoid using x:Key="styleName" and Style="{StaticResource styleName}"?

But more importantly I’m trying to understand why such a style binding doesn’t work always.

<ToolBar Height="25">
    <ToolBar.Resources>
        <Style TargetType="Separator">
            <Setter Property="Margin" Value="15"/>
        </Style>
        <Style TargetType="RadioButton">
            <Setter Property="Margin" Value="10"/>
            <Setter Property="Width" Value="50"/>
        </Style>
    </ToolBar.Resources>

    <RadioButton Content="A"/>  <!-- NOT APPLIED HERE -->
    <Separator/>                <!-- NOT APPLIED HERE -->
    <RadioButton Content="B"/>  <!-- NOT APPLIED HERE -->
</ToolBar>
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T06:55:39+00:00Added an answer on May 18, 2026 at 6:55 am

    WPF’s Toolbar does some funky things with its child controls. Unlike other containers, it’s not as simple as defining a style that applies to a type.

    Have a look at this blog post for some information that might help. Styling controls on a ToolBar.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Why doesn't this work: <Style TargetType=s:Substance> <Setter Property=Template> <Setter.Value> <DataTemplate> <StackPanel> <TextBlock Text={TemplateBinding Name}/>
Why doesn't this code work? I'am using FF. <head> <script type=text/javascript> document.getElementById(someID).onclick = function(){
Why doesn't sockets/remoting have the ability to work smoothly when disconnected and reconnected repeatedly?
Why doesn't this work? I have bypassed this before but i can't remember how
Doesn't work with other modules, but to give an example. I installed Text::CSV_XS with
Why doesn't the following code work? $('select option').live('click', function(){ alert('hello') }) html: <select class=ok>
Why doesn't this work as one may have naively expected? class Foo(object): def __init__(self):
Why doesn't my viewModel get inherited? I have the following viewModels: public class BaseViewModel
Doesn't an ORM usually involve doing something like a select *? If I have
Doesn't value have to return toString() to be able to call value.toString()? When do

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.