MaxCustomControls::MaxToolStrip Class Reference
Public Member Functions |
|
| MaxToolStrip () | |
| Constructor. |
|
| virtual void | UpdateColors () |
| Called when a change or update has occurred
in the application CUI system. |
|
Protected Member Functions |
|
| override void | WndProc (ref Message m) |
| Override the WndProc handler, so that the
WM_MOUSEACTIVATE message always activates the ToolStrip. |
|
Constructor & Destructor Documentation
| MaxCustomControls::MaxToolStrip::MaxToolStrip | ( | ) | [inline] |
Constructor.
Member Function Documentation
| virtual void MaxCustomControls::MaxToolStrip::UpdateColors | ( | ) | [inline, virtual] |
Called when a change or update has occurred in the application CUI system.
Clients implementing this interface should dynamically query the CUI system to acquire the new UI colors it should be using at the time of this method invocation.
- See also:
- ManagedServices.CuiUpdater
Implements MaxCustomControls::CuiUpdatable.
| override void MaxCustomControls::MaxToolStrip::WndProc | ( | ref Message | m | ) | [inline, protected] |
Override the WndProc handler, so that the WM_MOUSEACTIVATE message always activates the ToolStrip.
Otherwise if the host Form is a child window (consider the case of Material Explorer as Extended Viewport), clicking the ToolStrip won't activate the Form . Also, if the host Form is a child window and it's already active, the default .NET ToolStrip returns MA_ACTIVATEANDEAT for a WM_MOUSEACTIVATE message. This prevents the message to be properly handled: clicking on toolbar button won't really "hit" the button. Related essay: http://blogs.msdn.com/rickbrew/archive/2006/01/09/511003.aspx
- Parameters:
-
m Window message to be handled
