Opened 15 years ago
Closed 15 years ago
#4848 closed bug (fixed)
raw_char field in B_KEY_DOWN message when using input method
Reported by: | hiron | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
In pe editor, when I input Japanese characters by IM (input method), pe says "An OS error occurred: Name not found" and no characters are displayed. This is because pe checks the existance of "raw_char" field in a B_KEY_DOWN message (in PText::KeyDown()):
FailOSErr(Looper()->CurrentMessage()->FindInt32("raw_char", &ch));
On BeOS R5, I got 0x0a as "raw_char" value in B_KEY_DOWN message. I don't know why 0x0a is used but I never got other value on inputting text by IM.
On Haiku, BottomlineWindow for non-input-method-aware views doesn't put "raw_char" field in B_KEY_DOWN message. I tried to put it (as attached patch) and pe worked well this time.
Is this behavior intended one? : there may not be "raw_char" field in B_KEY_DOWN message. If so, it's not a Haiku's bug but a pe's.
Attachments (1)
Change History (2)
by , 15 years ago
Attachment: | put-raw_chars.patch added |
---|
comment:1 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Applied in hrev34180. Thanks!