Occurs when this element gets text in a device-independent manner.
Assembly: PresentationCore (in PresentationCore.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation
This event might already be marked as handled by the internal implementations of composited controls. See Remark below.
The event may already be marked as handled by the internal implementations of composited controls. For example, a TextBox is a composited control where the event is already marked as handled; within its compositing. Controls do this because the control needs to interpret some types of input, such as arrow keys, as having special meaning to that control. If you use PreviewTextInput as the event where you attach handlers for text input, you may receive better results. This technique circumvents most cases where control composition has already marked this event as handled and prevents your handler from receiving the event along the event route.
The event allows a component or application to listen for text input in a device-independent manner. The keyboard is the primary means of , but speech, handwriting, and other input devices can also raise .
Because of key combinations—either in default keyboards or through input method editors—multiple key events might raise just one text input event.
This event creates an alias for the TextCompositionManager.TextInput attached event for this class, so that is part of the class members list when UIElement is inherited as a base element. Event handlers that are attached to the event are attached to the underlying TextCompositionManager.TextInput attached event and receive the same event data instance.