Hi Nick, Ben, 2015-03-12 10:17 GMT+01:00 Ben Coman <b...@openinworld.com>:
> Hi Nick, > > The best way to ensure this will get included is log an issue and submit a > code slice at pharo.fogbugz.com. Then your code can undergo review and > be integrated in a managed way. > I've created an issue: https://pharo.fogbugz.com/default.asp?15121 > Read the "How to Contribute" link from there, and if its not clear, please > provide feedback so we can improve it. > > cheers -ben > > cheers -ben > > On Thu, Mar 12, 2015 at 4:37 PM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> Hi Nick, >> >> Thanks for chasing the bug down. >> >> Since the code for event handling is probably going to change in favor of >> SDL2 events soon, I think it should be good to also provide some tests for >> this, to detect any regression or problem, or at least to document expected >> behavior. Do you have any pointers of what should be tested? Which are the >> cases that worked or not and in which keyboard layouts? >> >> Guille >> >> El jue., 12 de mar. de 2015 a la(s) 8:48 a. m., Nick Doodka < >> nickdoo...@gmail.com> escribió: >> >> 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 <s...@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 >>>> <http://forum.world.st/Native-language-support-tp4809392p4811000.html> >>>> >>>> Sent from the Pharo Smalltalk Users mailing list archive >>>> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >>>> Nabble.com. >>>> >>> >>> >
