NM_INIT_*

  • Article

The NM_INIT_* constants define the NetMeeting 3 initialization options.

#define NM_INIT_NORMAL                0x00000000
#define NM_INIT_CONTROL               0x00000001
#define NM_INIT_NO_LAUNCH             0x00000002
#define NM_INIT_BACKGROUND            0x00000005

Elements

  • NM_INIT_NORMAL
    Default value. Starts NetMeeting as normal. The NetMeeting user interface (UI) is visible. See note following for changes in NetMeeting 3, including a recommendation to use NM_INIT_BACKGROUND as the initialization setting for client applications.
  • NM_INIT_CONTROL
    Request control of the NetMeeting UI. The NetMeeting UI is not visible. This is the only mode that receives all call notifications, including incoming call notifications from INmManagerNotify::CallCreated and then only when the NetMeeting UI is not active. If the NetMeeting UI is already active, then NM_INIT_CONTROL has the same effect as NM_INIT_NORMAL mode until the user closes the UI (by clicking close or exiting). At that time, the NM_INIT_CONTROL takes effect.
  • NM_INIT_NO_LAUNCH
    When a NetMeeting client calls INmManager::Initialize with this value, it means do not start NetMeeting services. However, the services may already be running at that point, in which case the call has no effect.

Initialization Specifics for NetMeeting 3

  • NM_INIT_BACKGROUND
    Keeps the NetMeeting UI hidden unless it's already running. NetMeeting is responsible for displaying dialogs and other UI elements. This is the recommended setting for NetMeeting client applications. Clients that initialize NetMeeting with this mode do not receive all the call notifications, because the NetMeeting UI is handling the events.

  • NM_INIT_NORMAL
    This mode now also receives outgoing call notifications.

    With secure calls introduced in NetMeeting 3, the following two cases do not generate call notifications from the NetMeeting run time:

    • If an incoming NetMeeting call is not secure and security is required.
    • If an incoming NetMeeting call is secure and security is disallowed.

Remarks

The following table explains the initialization modes.

Mode Constant Description
Background
(Recommended)		 NM_INIT_BACKGROUND Allows a NetMeeting client to run NetMeeting in the background so it can handle all the UI interactions. There is no visible NetMeeting window, but the NetMeeting icon appears in the taskbar notification area.
Normal NM_INIT_NORMAL The NetMeeting window is visible and NetMeeting is running.
In Control NM_INIT_CONTROL Allows a NetMeeting client to be in control of the NetMeeting services. The NetMeeting UI is not visible.
No Launch NM_INIT_NO_LAUNCH Allows a NetMeeting client to block the launch of NetMeeting services.

Requirements

**  Windows NT/2000:** Requires Windows NT 4.0 SP3 or later.
**  Windows 95/98:** Requires Windows 95 or later. Available as a redistributable for Windows 95.
**  Header:** Imsconf2.idl.

See Also

INmManager::Initialize