After series of trial and error methods I found acceptable solution of my problem. That is chunk of code from Pharo 2.0 should be copy&paste to appropriate place in method HandMorph>>generateKeyboardEvent. This way let me to avoid problems with mouse wheel freezing or generating errors.

i.e.
.....
"Adjustments to provide consistent key value data for different VM's:
- charCode always contains unicode code point.
- keyValue contains 0 if input is outside legacy range"
"If there is no unicode data in the event, assume keyValue contains a correct (<256) Unicode codepoint, and use that"
������ (charCode isNil or: [charCode = 0])
������ ������ ifTrue: [charCode := keyValue].
"If charCode is not single-byte, we definately have Unicode input. Nil keyValue to avoid garbage values from some VMs."
������ charCode > 255 ifTrue: [keyValue := 0].
.....

Full version of patched method I attach as zip-archive for v3 and v4 apart. I suppose developers should correct this method in next releases of Pharo for the sake non-english users support. Thanks for helping and advises.


2015-03-10 16:10 GMT+02:00 Sean P. DeNigris <sean@clipperadams.com>:
Now it is Pharo3.0 Latest update: #30862 and Pharo4.0 Latest update: #40474, but previous updates worked the same (ignore cyrillic capital letters ��������������)
What is the exact image version (incl. update number)?
I meant specifically regarding the #isArrow error. I don���t think you can be having this in 3.0, so you mean #40474 correct? Is it only after you change the language?
Cheers,
Sean


View this message in context: Re: Native language support

Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.