Issue 42932 - "Ctrl + K" results in "K" inside Writer
Summary: "Ctrl + K" results in "K" inside Writer
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 680m79
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords:
: 50191 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-02-16 17:17 UTC by ulf.stroehler
Modified: 2013-08-07 14:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ulf.stroehler 2005-02-16 17:17:21 UTC 
As reported by TZ undefined Ctrl sequences lead to normal characters inside Writer.

Examples:
=========

"Ctrl + k" results in "k"   (in english version)
"Ctrl + ä" results in "ä"  (in english version)
and so on.

Expectation:
============

Undefined Ctrl sequences shouldn't commit a character.
Comment 1 philipp.lohmann 2005-02-17 13:45:02 UTC 
can reproduce in 1.1.4, also.
Comment 2 philipp.lohmann 2005-02-17 14:14:20 UTC 
what had me puzzled was that the problem was not reproducible on windows; but
this is due to the fact that Ctrl-K delivers a character code of 11 on Windows 
(as opposed to 107 what you'd expect for 'k'). Ctrl-ä on the other hand gets a
character code of 0 on Windows, which is also not what one would expect. So on
windows the characters are not inserted because they are out of the legal value
range.

This makes the problem a writer issue since they ignore the pressed Ctrl key
when processing a key event (e.g. this doesn't happen in calc).
Comment 3 andreas.martens 2005-02-17 17:17:05 UTC 
Due a lack of resources retargetted to OOoLater.
Comment 4 thorsten.ziehm 2005-02-18 10:53:28 UTC 
This task hinder you to work effetively with Ctrl-keys on UNIX. Therefore I
retarget this task to OOo2.0.1, but when the feedback is high, than we have to
fix it until OOo2.0.
Comment 5 andreas.martens 2005-02-21 10:33:45 UTC 
Should be feasible?!
Comment 6 Oliver Specht 2005-02-21 12:09:51 UTC 
It's to easy to let it wait for PP1. Target changed to 2.0
Fixed in sw/source/ui/docvw/edtwin.cxx in cws os54
Comment 7 Oliver Specht 2005-03-04 12:10:08 UTC 
cws os54 is available on so-cwsserv04

re-open issue and reassign to us@openoffice.org
Comment 8 Oliver Specht 2005-03-04 12:10:13 UTC 
reassign to us@openoffice.org
Comment 9 Oliver Specht 2005-03-04 12:10:17 UTC 
reset resolution to FIXED
Comment 10 ulf.stroehler 2005-03-07 15:44:34 UTC 
Verified on CWS 'os54'.
Comment 11 frank.meies 2005-03-21 13:09:37 UTC 
Reopened because this fix resulted in i45069, which in turn gave us i45629.
Comment 12 frank.meies 2005-03-21 13:10:18 UTC 
Set target back to 'OOo 2.0.1'.
Comment 13 Oliver Specht 2005-05-18 11:36:57 UTC 
Now finally fixed in cws os62 in 
sw/source/ui/docvw/edtwin.cxx
Comment 14 Oliver Specht 2005-06-02 07:38:39 UTC 
*** Issue 50191 has been marked as a duplicate of this issue. ***
Comment 15 Oliver Specht 2005-06-29 12:38:18 UTC 
cws os62 can be found on cws03

re-open issue and reassign to us@openoffice.org
Comment 16 Oliver Specht 2005-06-29 12:38:24 UTC 
reassign to us@openoffice.org
Comment 17 Oliver Specht 2005-06-29 12:38:31 UTC 
reset resolution to FIXED
Comment 18 ulf.stroehler 2005-09-23 09:47:16 UTC 
Verified in cws 'os62'.
Comment 19 ulf.stroehler 2005-11-28 10:48:17 UTC 
verified in m142.