Reference » Messages



Detailed explanation of every message (aka event or note) used by Elgrint.


Name Description
ChildListChanged One or more child windows of this window have been opened or closed.
CursorMoved Input event from a screen pointing device (mouse, touchpad, touchpoint, pen, etc).
DirectoryChanged A non-fixed drive has been activated or deactivated.
DirectoryChanging An existing data carrier is about to be removed - the data on it can still be accessed, but not for long.
EnablingChanged Window's enabling state changed (window was enabled or disabled).
FocusChanged Window's focus state has changed (window gained or lost the input focus).
HotChanged Window's hot state changes (window gained or lost the hot state).
KeysEntered Input event from a keyboard, keypad, mouse button, touchpad, or mouse wheel.
Moved Window's position relatively to its parent's top-left corner (including z-order) has changed.
Notice Window has generated a custom event using MWindow::genNotice.
Paint Informs the window that its graphical content needs to be repainted right now.
RectChanging Window's size and/or position (including z-order) are about to change.
RemoteNotice External custom event has been generated by another thread or another process.
Resized Window's size has changed.
StringEntered Derived input event - keyboard input translated into characters.
SystemResumed System has been reactivated after a sleep or an hibernation mode.
SystemSuspending System is about to enter a sleep/hibernation mode, or is shutting down.
TimerExpired Input event from the system clock that signals an expiration of a preset timer.


Messages report various events, which can have interest to the app's windows. Windows receive these messages through special overloadable methods called message handlers. Each message named XXXX has a corresponding mcXXXX numeric identifier (a member of the MMessageCode enumeration), the void OnXXXX() handler (protected virtual method of MWindow), and an ON_XXXX macro for a more convenient overloading of the corresponding handler.


There are three types of messages, depending on their relationship with the corresponding event: post-message, pre-message, and request-message (aka in-message).

This leaves out the custom messages - Notice and RemoteNotice, which can serve as any of the above types.


Messages can also be grouped in a different way, according to the source that causes the corresponding event. Then, there are three kinds of events: input, presentation, and system.


Finally, messages can be either queued, or non-queued (aka stacked), depending on the way they are delivered.


Let us know

Please Contact us to report any errors on this page, or to suggest any improvements.

Miranor Home | About Miranor | About Elgrint | Create account | Login | Account settings | Contact Us | Privacy Policy | Site map

© Copyright 2014 by Miranor. All rights reserved. By using this site you agree to the Terms of Use.

Page last updated on August 10th, 2014.