Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function enables an input method editor (IME) to generate messages that are sent to the window associated with the input method context (IMC). These messages are stored in the hMsgBufmember of the INPUTCONTEXTstructure identified by the hIMCparameter.

Syntax

BOOL WINAPI ImmGenerateMessage( 
  HIMC 
hIMC
);
	

Parameters

hIMC

[in] Handle to the INPUTCONTEXTstructure that contains IME messages in its hMsgBufmember.

Return Value

TRUE indicates success. FALSE indicates failure.

Remarks

This is a general purpose function, but it is typically called by an IME when the input method manager (IMM) calls the ImmNotifyIMEfunction to notify an IMEof a context update.

An IMEuser interface (UI) should not call this function only to update UI appearance. Instead, the IMEUI should be updated when the IME is informed about an updated IMC. It is recommended that this function be used by an IME only when the IME changes the IMC without any keystroke activity from the user and needs to inform an application of the change.

Requirements

Header imm.h
Library Coreimm.lib
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.