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 method sends a series of WM_KEYUPor WM_KEYDOWNmessages from the input method (IM) to the window with the focus.

Syntax 

HRESULT SendCharEvents( 
  UINT 
uVK, 
  UINT 
uKeyFlags, 
  UINT 
uChars,
  UINT* 
puShift, 
  UINT* 
puChars
);

Parameters

uVK

Virtual key code sent in the first WM_KEYUP or WM_KEYDOWN message generated as a result of this method.

uKeyFlags

Unsigned integer that contains flags describing the state of the first key sent by this method. These flags are translated into the lKeyDataparameter of the first message. See Keybd.h for the legally defined values. If the KeyStateDownFlag bit is set, this method generates a WM_KEYDOWN message; otherwise, it generates a WM_KEYUP message.

uChars

Number of characters in puChars.

puShift

Pointer to a buffer containing the corresponding KEY_STATE_FLAGS for the characters in puChars. See Keybd.h for the legally defined values. These flags should be identical to the flags in uKeyFlags.

puChars

Pointer to a buffer containing the all characters but the first one sent by this method.

Return Value

An appropriate HRESULTvalue is returned.

Remarks

This method allows the IM to determine its own keyboard layout, because it can associate any virtual key with any character and key state.

Another way to send characters to the active window is by means of the IIMCallback::SendStringand IIMCallback::SendVirtualKeymethods.

Unlike IIMCallback::SendVirtualKey, this method does not affect the global key state.

Requirements

Header sip.h
Library uuid.lib
Windows Embedded CE Windows CE 2.01 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.