Neil Hodgson
2013-09-16 02:40:43 UTC
Trying to clean up archaic cruft in the Cocoa platform layer and found code that handles WM_UNICHAR by converting to a string and inserting that string at the caret. WM_UNICHAR was originally from Windows where it is posted by the system. The Carbon platform layer implemented WM_UNICHAR but did not call it. It has never been exposed in a header to allow use by client code.
This may have been added on Carbon to allow the application to perform input, possibly for macros or an alternate input scheme such as a vi emulation mode. Can anyone recall what purpose it served on Carbon and whether the Cocoa implementation was added simply to match the Carbon implementation?
Neil
This may have been added on Carbon to allow the application to perform input, possibly for macros or an alternate input scheme such as a vi emulation mode. Can anyone recall what purpose it served on Carbon and whether the Cocoa implementation was added simply to match the Carbon implementation?
Neil
--
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scintilla-interest+***@googlegroups.com.
To post to this group, send email to scintilla-***@googlegroups.com.
Visit this group at http://groups.google.com/group/scintilla-interest.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scintilla-interest+***@googlegroups.com.
To post to this group, send email to scintilla-***@googlegroups.com.
Visit this group at http://groups.google.com/group/scintilla-interest.
For more options, visit https://groups.google.com/groups/opt_out.