pq26075 Creating DBCS chars in MLE does not show first byte
----------------------------------------------------------------------------------------------------

Affected Platforms:

Windows 95, Windows98


Affected Features:

Base Smalltalk

Prerequisites:

v4.5a

Symptom:

Using a multi-line edit field under Win95 or 98
Shift into Korean.  Press r, then k.
(this is a valid Korean character).
You will notice that the first character r, which 
represents half of the completed DBCS character, does NOT
show up in the MLE, but rather it shows down in the IME.

If you do the same test using Notepad, you will notice that this
interim first character shows up in the Notepad MLE.  This is
what the customer expects to be the correct behavior.  They
should not have to look down to the IME to make sure they
are keying in the correct first half of a DBCS character.

Workaround:

The native text widget on Windows 95 and 98 has a limit of about 32K.
 To get around this limit, we were forced to write our own text widget.
 This is the ONLY REASON we did this.  Anyways, it's called OSLargeText,
 it's PRIVATE to the implementation of Commmon Widgets and it is used
 only on Windows 95 and 98.  On NT, the native text widget is used.

 OSLargeText does not support the IME.  So, if a customer is willing to
 live with the limit, it is possible to use the native text widget on
 Windows 95 and 98.

 To force Smalltalk to use the native text widget on Windows, evaluate
this expression and save the image:

  CwText largeText: false.

 Set this value to true to use the emulated text widget.  This expression
has no effect on other platforms.