3
Vote

WPF Ribbon application menu alignment problem.

description

I'm using WPF 4's (in .NET 4) ribbon control, version 3.5.40729.1, in my application (edit: It also happens with the newly released version 4.0.0.11019). The application menu and all sub-menu popups align as far left as possible, usually far outside the ribbon window. The expected location is that the application menu's left edge aligns with the ribbon window's left edge, and that sub-menu popups will align with the left edge of the right (usually recent items) content pane.
 
Even if just create a brand new ribbonwindow project and run it, the bug happens.
 
I've attached a screenshot to illustrate.
 
I also posted about this issue on the msdn forums: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/3f54d763-fbd1-47bd-8e2a-afbdc3e2f737

file attachments

comments

MarioC wrote Jan 3, 2011 at 11:02 PM

Same problem here. For the record, I'm running Windows 7 Ultimate x64 EN.

MarioC wrote Jan 5, 2011 at 3:30 PM

Several reboots and reinstalls later, I found out what was causing the issue, at least in my case.

When the Tablet input is enabled and set for right-handed use, the Popup control aligns to the right edge of its placement target, instead of the left one, presumably to prevent the writing hand from obscuring the popup. As the ApplicationMenu of the Ribbon control is rendered through a Popup, this causes the issue reported.

While this behavior might make sense for popups in general (although it would be nice if such things were documented somewhere) it makes the WPF Ribbon control inconsistent with the other ribbons out there that just disregard this specific situation.

quillaja wrote Jan 5, 2011 at 7:10 PM

@MarioC: You're brilliant! This problem has been bothering me for months. It seems the problem I encountered was the same as you... because when I changed the handedness of my Tablet PC to "left", the menus in the ribbon control began to work as expected.

The thing is, this problem never appeared for any other ribbon applications besides the ones I've made myself. However, those might be using different APIs and libraries than the wpf ribbon.

Anyway, I hope that this issue will be fixed now that the problem has been identified. Thank you again!

wrote Jan 26, 2012 at 2:03 AM

wrote Feb 22, 2013 at 1:40 AM

fw wrote Nov 22, 2016 at 11:50 AM

Impact: Low?? It's still an issue, 2016! And this is the very show stopper for we have to use another Control!