Bug 57669 - Naming/renaming completion in tree view is clumsy
Summary: Naming/renaming completion in tree view is clumsy
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: 1.1.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-24 23:03 UTC by Stevan White
Modified: 2004-06-13 14:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stevan White 2003-04-24 23:03:08 UTC
Version:           1.1.1 (using KDE KDE 3.1)
OS:          Linux

When naming a new item or re-naming an existing item in the tree view, you have to hit 'enter' to terminate the action.  If you click elsewhere while changing the name, usually nothing happens--you can't select anything. 

Sometimes, I find clicking around eventually does something, but the re-naming is cancelled, or the new item disappears. (This may be a separate bug, but the following suggestion fixes it anyway.)

In most modern interfaces, it is enough to click outside a text field to finish an edit action.  Here, of course, the name has to be valid: non-null, alphanumeric, and unique.

If the mouse is clicked outside of the name box in question, the name should be validated, and if valid, the naming/re-naming should be completed and the click processed further (possibly to select another item). If the name is not valid, an alert dialog should be raised explaining this to the user, and the edit should continue.
Comment 1 Sebastian Stein 2003-09-10 10:14:10 UTC
Subject: Re: Naming/renaming completion in tree view is clumsy

Thank you for your bug report.
The bug that you reported has been identified and has been fixed in the
latest development (CVS) version of KDE. The bug report will be closed.

Comment 2 Sebastian Stein 2003-09-10 10:21:17 UTC
*** Bug has been marked as fixed ***.
Comment 3 Stevan White 2004-06-13 14:40:48 UTC
Problem is gone in 1.2.1.