Bug 245722 - "PDE Tools > Externalize Strings" dialog should allow TAB to take you to the next "Substitution Key" field
Summary: "PDE Tools > Externalize Strings" dialog should allow TAB to take you to the ...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2008-08-29 12:27 EDT by Simon Archer CLA
Modified: 2019-09-09 02:31 EDT (History)
1 user (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Archer CLA 2008-08-29 12:27:58 EDT 
When working with the "PDE Tools > Externalize Strings" dialog I typically want to edit every suggested key in the "Substitution Key" column of the table.

Currently, when you press the TAB key the focus is transferred to the Source widget, which is never what I want.  Instead, pressing TAB should take you to the next row in the table and enter edit-mode so that you can update the field.

Without this support, you have to constantly grab the mouse, which is no fun at all.
Comment 1 Chris Aniszczyk CLA 2008-08-29 12:31:58 EDT 
Thanks for the report Simon.

Marking this for bugday
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:16:41 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Julian Honnen CLA 2019-09-09 02:31:14 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.