To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108417
                 Issue #|108417
                 Summary|Existing file privacy password GUI niggle across all O
                        |Oo apps.
               Component|framework
                 Version|OOO310m9
                Platform|PC
                     URL|
              OS/Version|Windows Vista
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|ui
             Assigned to|tm
             Reported by|oldwiseowls





------- Additional comments from [email protected] Mon Jan 18 13:05:57 
+0000 2010 -------
Acquiring a new native OOo format file password generates a classic double text 
entry box vis. enter password / confirm password with the classic OK, Cancel 
and 
Help buttons where the OK button is the shadowed default so following the text 
entry with a CR is the time accepted method.

However, for existing native OOo format file passwords, a single text entry box 
is generated where the OK button is not either shadowed or the CR default so 
one 
has to grab the mouse to execute.

I have used three versions of OOo for more than 2 years and it rocks. If I have 
overlooked or missed this minor niggle as an existing / solved issue, I 
apologise.

John

---------------------------------------------------------------------
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]

Reply via email to