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
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.
Read the How to Contribute link from there, and if its not clear, please
provide feedback so we can improve
Hi Nick,
thanks for finding this. I can now, finally, use the compose key on my
Linux keyboard to enter characters like Ç, É, À...
Thierry
2015-03-12 8:48 GMT+01:00 Nick Doodka nickdoo...@gmail.com:
After series of trial and error methods I found acceptable solution of my
problem. That is
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:
2015-03-12 14:41 GMT+01:00 Henrik Johansen henrik.s.johan...@veloxit.no:
On 12 Mar 2015, at 10:39 , Thierry Goubier thierry.goub...@gmail.com
wrote:
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
Hi nick
We would love that you can.
Now we need somebody with a non ascii language to help.
Stef
Le 4/3/15 10:37, Nick Doodka a écrit :
Hi all.
I would like to use Pharo in my native language (Ukrainian in my case
or Cyrillic), but I cannot enter some capital letters to Workspace /
System
On 12 Mar 2015, at 10:39 , Thierry Goubier thierry.goub...@gmail.com wrote:
Hi Nick, Ben,
2015-03-12 10:17 GMT+01:00 Ben Coman b...@openinworld.com
mailto:b...@openinworld.com:
Hi Nick,
The best way to ensure this will get included is log an issue and submit a
code slice at
Hello Marcus.
Your patch solves my problem with capital letters. But it raises another
trouble - every mouse wheel move or keyboard shortcut like ctrl+key cause
next error MessageNotUnderstood:CharacterisArrow.
2015-03-07 12:39 GMT+02:00 Marcus Denker marcus.den...@inria.fr:
I got a mail that
Nick Doodka wrote
next error MessageNotUnderstood:CharacterisArrow.
What is the exact image version (incl. update number)?
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Native-language-support-tp4809392p4810892.html
Sent from the Pharo Smalltalk Users mailing list
Now it is Pharo3.0 Latest update: #30862 and Pharo4.0 Latest update:
#40474, but previous updates worked the same (ignore cyrillic capital
letters ЁНПОЛЄМ).
2015-03-10 13:06 GMT+02:00 Sean P. DeNigris s...@clipperadams.com:
Nick Doodka wrote
next error MessageNotUnderstood:CharacterisArrow.
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
I got a mail that suggest a fix:
https://pharo.fogbugz.com/f/cases/15085/non-english-character-input
(I have attached it as a file-out, you can just drag-n-drop it on the pharo
desktop)
We should check if that solves the problem.
On Wed, Mar 4, 2015 at 10:37 AM, Nick Doodka nickdoo...@gmail.com
Hi all.
I would like to use Pharo in my native language (Ukrainian in my case or
Cyrillic), but I cannot enter some capital letters to Workspace / System
Browser because it's fails on letters: CapsLock or Shift+Keys -
[~YGJKV].
That behavior take place only in Pharo ver. 3 and 4. In Pharo 2.0 all
13 matches
Mail list logo
