<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx</link><description>Split Button in WPF</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx#877406</link><pubDate>Fri, 27 Oct 2006 00:28:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:877406</guid><dc:creator>Joe</dc:creator><description>&lt;p&gt;I am having problems with the &amp;lt;mwt:ButtonChrome&amp;gt; tag. &amp;nbsp;I added this:&lt;/p&gt;
&lt;p&gt;xmlns:mwt=&amp;quot;clr-namespace:Microsoft.Windows.Themes;assembly=PresentationFramework.Royale&amp;quot;&lt;/p&gt;
&lt;p&gt;to the top but I still get an error that says:&lt;/p&gt;
&lt;p&gt;The tag 'ButtonChrome' does not exist in XML namespace 'clr-namespace:Microsoft.Windows.Themes;assembly=PresentationFramework.Royale'.&lt;/p&gt;
&lt;p&gt;Any thoughts?&lt;/p&gt;
</description></item><item><title>re: Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx#877541</link><pubDate>Fri, 27 Oct 2006 02:26:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:877541</guid><dc:creator>llester</dc:creator><description>&lt;p&gt;check to see that you have the PresentationFramework.Royale dll referenced in the project....&lt;/p&gt;
</description></item><item><title>re: Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx#894415</link><pubDate>Sun, 29 Oct 2006 14:15:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:894415</guid><dc:creator>Andy Wilkinson</dc:creator><description>&lt;p&gt;Thanks a lot for the idea Lester. The ContextMenu method works well, but what if you want a &amp;quot;real&amp;quot; context menu too? Well, I had a play around and posted a blog entry with an adapted version of this control at,&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://andyonwpf.blogspot.com/2006/10/dropdownbuttons-in-wpf.html"&gt;http://andyonwpf.blogspot.com/2006/10/dropdownbuttons-in-wpf.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx#896565</link><pubDate>Sun, 29 Oct 2006 20:29:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:896565</guid><dc:creator>llester</dc:creator><description>&lt;p&gt;yeah the above does assume that you would not require a normal context menu... as a button doesnt normally provide that and it is also counter intuitive...&lt;/p&gt;
</description></item><item><title>re: Split Button in WPF</title><link>http://blogs.msdn.com/llobo/archive/2006/10/25/Split-Button-in-WPF.aspx#904145</link><pubDate>Mon, 30 Oct 2006 21:52:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:904145</guid><dc:creator>Andy Wilkinson</dc:creator><description>&lt;p&gt;Very good point. I can't think of any time I've seen a button with a context menu. In fact, if a button had some form on menu associated with it, I'd expect a split-button anyway.&lt;/p&gt;
&lt;p&gt;Your solution also has the advantage that you don't even need to create a custom control, just a normal button with a context menu and your code in a Click handler in the Window class for example. This solution I feel is the best one if you are writing a UI and just want to add a split button to get the job done.&lt;/p&gt;
&lt;p&gt;In my case I'm trying to in the end write a control library. In this situation, who am I to tell the user of the control how they should be using it? In fact in WPF this becomes more of an issue - after all, the control user can style it to look nothing like a button any longer. Maybe even a situation where a drop-down and a context menu are applicable. In this case I prefer my more flexible implementation.&lt;/p&gt;
</description></item></channel></rss>