Issue 61765 - Tools/Customize: Insufficient design of Keyboard-Tab
Summary: Tools/Customize: Insufficient design of Keyboard-Tab
Status: CONFIRMED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-08 06:24 UTC by joerg.skottke
Modified: 2013-02-07 21:50 UTC (History)
3 users (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 joerg.skottke 2006-02-08 06:24:18 UTC 
When calling the Tools/Customize dialog from either the backing window or via
Tools/Macros...->Assign the keyboard tab is not displayed.

This is incorrect behavior which was introduced because there exists a
radiobutton that allows to choose between assigning the shortcut to either the
entire office or the application only. This is somewhat problematic in relation
to backing window or assigning macros, the application is not set or undefined.

Affected automated testcases:
f_updt_customize.bas::tUpdtCustomize
f_basic_first.bas::tMacro_Dialog
Comment 1 stefan.baltzer 2006-02-10 17:06:31 UTC 
SBA->CD: Please have a look. 
It affects automated testing, so please contact JSK about the urgency.
I am undecided about what target to set. So target "OOo 2.03" is mainly a
motivation to do so :-)
Comment 2 carsten.driesner 2006-02-14 09:57:17 UTC 
cd->jsk: This behavior was defined by user experience. It's from your point of
view "incorrect". As the current behavior works as designed, we have to ask user
experience to change it.
cd->fl,cj: Can you please comment to this issue.
Comment 3 frank.loehmann 2006-02-14 18:09:56 UTC 
FL: JSK is right. Configuration is also possible for entire OOo via radio button
if called from an application. Should be changed, but I don't think that this is
so urgent to fix this for PP3. So if it is no big issue for automatic testing, I
would propose “OOo 3.0†as new target. Owner could be CJ or myself.
Comment 4 joerg.skottke 2006-02-20 08:25:27 UTC 
Set target to 3.0
Comment 5 carsten.driesner 2006-02-20 08:30:30 UTC 
cd: Accepted.
Comment 6 carsten.driesner 2006-07-04 13:48:38 UTC 
cd: Set target to OOo 2.x.
Comment 7 carsten.driesner 2007-10-15 09:28:41 UTC 
cd->fl: Please take over. It's about the keyboard customize dialog design.
Comment 8 frank.loehmann 2007-11-08 09:32:22 UTC 
No resources for OOo 2.x -> retargeted to OOo 3.x.