[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Accelerator rework? (workbench eats Control+Z)
|
This is covered by one of the "top ten" issues for 2.1.
http://www.eclipse.org/eclipse/development/challenges_2_1.html
Work on this is about to be set up.
Kai
Randy Hudson
<hudsonr@xxxxxxxxxx> To: platform-ui-dev@xxxxxxxxxxx, platform-swt-dev@xxxxxxxxxxx
Sent by: cc:
platform-ui-dev-admin@ Subject: [platform-ui-dev] Accelerator rework? (workbench eats Control+Z)
eclipse.org
09/18/2002 05:51 PM
Please respond to
platform-ui-dev
Are any 2.1 plans underway to solve the accelerator problem. The problem
is that a Control cannot receive a keystroke if it is registered somewhere
in the Menu. A related problem is that a child Control has focus, and you
would like certain keystroked to get promoted to a parent or ancestor (like
PAGE_UP in the PDE's plugin.xml editor).
For those unfamiliar with the problem, the Workbench registers Actions with
Control+Z and other accelerators. As a result, Native controls will not
receive undo keystrokes, etc. The workaround required by UI developers
who have an editor filled with Text controls in cumbersome. You must
register an action for Undo with the workbench. That action must enable
and disable as a result of each change on every text control in the editor,
and it must follow focus, and it must forward the undo action to the
control. If anyone extends your Editor and adds a new page to it, you'd
better plan for a UndoRedoCutCopyPasteHelper as well, if you want those
functions on that page.
In addition to Undo/Redo/Cut/Copy/Paste, there are tons of other problems
that result from the current keyboard handling. For example, accessibility
is broken whenever the Java Editor is up. I cannot use Control+SPACE to
toggle selection in any tree, table, or other control in the workbench.
