usnotifycode (USHORT)

      Notify code.

      MLN_TEXTOVERFLOW

        A key stroke causes the amount of text to exceed the limit on the number of bytes of data (refer to MLM_SETTEXTLIMIT). The parameter contains the number of bytes of data which would not fit within the current text limit. For character key strokes this can be 1 or 2 (DBCS). For Shift+Ins (paste) it can be any amount up to the paste limit.

        The default rc of FALSE causes the default error handling, which is to ignore the key stroke, and beep.

        An rc of TRUE implies that corrective action has been taken (such as deleting existing text or raising the limit) and the WM_CHAR (in Multiline Entry Fields) should be reprocessed as if just entered.

      MLN_PIXHORZOVERFLOW
        A key stroke causes the size of the display bit map to exceed the horizontal limit of the format rectangle (refer to MLM_SETFORMATRECT). The parameter contains the number of pels that would not fit within the current text limit.

        The default rc of FALSE causes the default error handling, which is to ignore the key stroke, and beep.

        An rc of TRUE implies that corrective action has been taken (such as changing to a smaller font or raising the limit) and the WM_CHAR (in Multiline Entry Fields) should be reprocessed as if just entered.

      MLN_PIXVERTOVERFLOW
        A key stroke causes the size of the display bit map to exceed the vertical limit of the format rectangle (refer to MLM_SETFORMATRECT). The parameter contains the number of pels that would not fit within the current text limit.

        The default rc of FALSE causes the default error handling, which is to ignore the key stroke, and beep.

        An rc of TRUE implies that corrective action has been taken (such as changing to a smaller font or raising the limit) and the WM_CHAR (in Multiline Entry Fields) should be reprocessed as if just entered.

      MLN_OVERFLOW
        An action other than entry of a key stroke causes a condition involving the text limit or format rectangle limit, such that either the limit becomes inadequate to contain the text or the text exceeds the limit.

        This can be caused by:

          MLM_SETWRAP
          MLM_SETTABSTOP
          MLM_SETFONT
          MLM_IMPORT
          MLM_PASTE
          MLM_CUT
          MLM_UNDO
          MLM_DELETE
          WM_SIZE.

        MLN_HSCROLL
          Indicates that the MLE has completed a scrolling calculation and is about to update the display accordingly. All queries return values as if the scrolling were complete. However, no scrolling action is visible on the user interface.
        MLN_VSCROLL
          Indicates that the MLE has completed a scrolling calculation and is about to update the display accordingly. All queries return values as if the scrolling were complete. However, no scrolling action is visible on the user interface.
        MLN_CHANGE
          Signals that the text has changed. This notification is sent whenever any text change occurs.
        MLN_UNDOOVERFLOW
          Signals that the text change operation, which could normally be undone, cannot be undone because the amount of text involved exceeds the undo capability. This includes text entry, deletion, cutting, and pasting.
        MLN_CLPBDFAIL
          Signals that a clipboard operation failed.
        MLN_MEMERROR
          Signals that the required storage cannot be obtained. The action that results in the increased storage requirement fails.
        MLN_SETFOCUS
          Sent whenever the MLE window receives the input focus.
        MLN_KILLFOCUS
          Sent whenever the MLE window loses the input focus.
        MLN_MARGIN
          Whenever the user moves the mouse into the left, right top, or bottom margins, this message is sent to the owner of the window.

          If the owner returns an rc of TRUE, the mouse move is assumed to have been processed by the owner and no further action need be taken.

          If the owner returns an rc of FALSE, the MLE performs a default action appropriate to each different mouse action.

          The exceptions to this are all mouse messages that occur after a button-down inside the margin, until and including the matching button-up. Conceptually the drag (button-down until button-up) is a single macro event. Therefore, if FALSE is returned for a button-down event, no further margin notifications are given until after the drag has ended (button-up).

          Note: If the application receives a notification of button-down in the margin and processes it, it must capture the mouse until the button-up event.

        MLN_SEARCHPAUSE
          This notification is sent periodically by the MLE, while an MLM_SEARCH message is being processed, to give an application the opportunity to stop excessively long searches, and to provide search progress information. The owner window can respond either with TRUE or FALSE. FALSE causes the MLE to continue searching; TRUE causes the MLE to stop the search immediately. For further information, see MLM_SEARCH

        [Back] [Next]