To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=69992
------- Additional comments from [EMAIL PROTECTED] Wed Oct 4 02:53:06 -0700 2006 ------- Weird isn't it, yes they keep their own list of chars pressed and know that a o was already just pressed, so if another one is entered after a previous one within a given time a backspace is emitted to get rid of the character committed by the 1st o and then a replacement char is commited. It does actually work for standard gtk and kde apps. Now in OOo when the backspace comes what happens is something like this... it gets handled by VCL normally which sends it onwards and somewhere along the line (in sfx2 IIRC) the writer backspace handler gets dispatched, which boils down to something like PostUserEvent back in vcl, which puts calling the callback as an idle handler onto the gtk event queue, but the queue doesn't get a chance to get processed before the next o arrives through commit. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
