Bug 259502 - [KHotKeys] Unable to input special character
Summary: [KHotKeys] Unable to input special character
Status: RESOLVED INTENTIONAL
Alias: None
Product: khotkeys
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
: 82260 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-12-11 09:07 UTC by Lach Sławomir
Modified: 2015-10-18 07:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lach Sławomir 2010-12-11 09:07:41 UTC
Version:           unspecified (using KDE 4.5.85) 
OS:                Linux



Reproducible: Always

Steps to Reproduce:
Create new and simple gesture. Open Special Character Addition Tools in OpenOffice. Copy euro/alpha sign to action tab. Save changes and try to insert this character by a gesture. Change now character to a letter. Try to insert a letter now.

Actual Results:  
Special character wasn't inserted - no matter of active window.

Expected Results:  
I can insert Euro/Alpha/other signs.

KDE Application and GTK+ are affected by this bug. I think, that is a KHotKeys based bug.
Comment 1 Thomas Lübking 2015-10-15 15:03:42 UTC
> I think, that is a KHotKeys based bug.
Yesno.
It's not trivial to XSendEvent a synthetic unicode, because XKeycodeToKeysym will fail on it.
It would be required to map the unicode into another code. Then xsync, wait some time (until the receiving client hopefully handled the input) and change back the mapping. Ughh.

=> This will not fix, what might be a possible solution somewhere somewhen is to support pasting text (though afaik, you cannot just past the secondary selection buffer to another client, so you'd have to operate on the primary buffer and fake a 3rd mouse button press, what ends up in a paste wherever the mouse currently is)
Comment 2 Thomas Lübking 2015-10-18 07:09:53 UTC
*** Bug 82260 has been marked as a duplicate of this bug. ***