long term possibility: uiArea text event handling

[andlabs]

This is for gathering information needed in order to allow a future version of uiArea to be used for text input as well as raw keyboard input.

Cocoa https://developer.apple.com/library/mac/documentation/TextFonts/Conceptual/CocoaTextArchitecture/TextEditing/TextEditing.html#//apple_ref/doc/uid/TP40009459-CH3-SW3 https://developer.apple.com/library/mac/documentation/Cocoa/Reference/NSTextInputContext_Class/ https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/TextDefaultsBindings.html#//apple_ref/doc/uid/20000468

[andlabs]

Windows http://www.catch22.net/tuts/unicode-text-editing The problem here is that TranslateMessage() is documented as ALWAYS returning TRUE on a key-down event, so there's no way to know whether we should ignore the current one because a WM_CHAR is coming up or not :| ImmContext functions judging from tsfapp samples? Are we just supposed to know which keys contribute to text?

[andlabs]

Potential problem: Cocoa uses predefined navigational and editing shortcuts, some of which come as part of the text event system and others as part of menus.

[andlabs]

GTK+ GtkIMContext GtkSettings gtk-im-module GtkIMMulticontext gtk_im_multicontext_set_context_id()

[andlabs]

Windows there's shell facilities for touch screens that automatically pop up a keyboard on EDIT controls:

• https://msdn.microsoft.com/en-us/library/windows/desktop/jj126268(v=vs.85).aspx
• https://blogs.msdn.microsoft.com/oldnewthing/20150601-00/?p=45481
• https://blogs.msdn.microsoft.com/oldnewthing/20150608-00/?p=45431
• http://stackoverflow.com/questions/38774139/show-touch-keyboard-tabtip-exe-in-windows-10-anniversary-edition#comment64922814_38774139

see if there's a way we can opt into this behavior for other window classes