dboitnott said 9 months, 3 weeks ago:
It would appear that C1RibbonForm (or perhaps C1Ribbon itself) is not posting (or perhaps forwarding) WM_SYSCOMMAND messages properly when the user clicks the "command box" controls that are being drawn on the ribbon when an MDI child is maximized.
My scenario: my MDI child forms each have a status bar on them (a StatusStrip object). I need to keep this status bar updated regularly, and one way I am doing this is by watching for SYSCOMMAND messages using an override of WndProc in the child form. In this method, I am watching for WM_SYSCOMMAND (0×0112) and when that occurs, further evaluating the wParam for one of SC_MAXIMIZE (0xF030), SC_MINIMIZE (0xF020), or SC_RESTORE (0xF120).
When I click the Windows default control box icons on a NON-maximized child, I get these messages without issue. However, if I maximize the MDI child, and then click one of the control box icons on the ribbon (minimize or restore), I do _not_ get the messages.
Based on this, it would appear that the Ribbon control is not properly announcing the events.
C1_AndreyD23p said 9 months, 3 weeks ago:
The issue must be fixed in C1Ribbon build 2/4.0.20122.396. The WM_SYSCOMMAND message is now posted as expected. Here is attached the latest build for .NET 2.0 (please unblock .zip file before extracting its contents – select Properties from the context menu, then press the Unblock button at the bottom of the General tab).
Attachments:You must be logged in to view attched files.Answerdboitnott said 9 months, 3 weeks ago:
Thank you, Andrey. I have verified that it is now posting the messages.Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.