Bug 291204 - Save as Dialog box, Name field should not populate from file listing area, unless deliberately selected.
Summary: Save as Dialog box, Name field should not populate from file listing area, u...
Status: RESOLVED DUPLICATE of bug 102972
Alias: None
Product: kfile
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-10 19:53 UTC by Aaron Peterson
Modified: 2018-04-11 20:45 UTC (History)
1 user (show)

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 Aaron Peterson 2012-01-10 19:53:34 UTC
Version:           CVS (using Devel) 
OS:                Linux

A single click in a save as dialog box, should not populate the File Name field, 

Some people have a bad memories, and sometimes forget what file one is working on.

If I click on a file, it should receive focus, Not selection.

If I double click on a file, that would be an acceptable deliberate action.
If I right click on a file, and say use this name, that would be acceptable.



Reproducible: Always

Steps to Reproduce:
I used kate,
file - save as
type in a name that fits what you are working on.
you slip your mouse, use an apple pointing device, or cat clicks on your most important document that is named similar...
look back, hit save,

wonder why it is asking for overwrite?





Actual Results:  
an existing file is being set up to be overwritten.  Thankfully the dialog system... chooses cancel as default.

Expected Results:  
a stray click would not overwrite the name I wrote in the name field. (and would not populate it if it were blank--perhaps populate it with an incremented number if it were blank)

I believe I am proposing behavior that is different from other desktop systems, so perhaps implementing this as an option would be wise.
Comment 1 Nate Graham 2018-04-10 20:42:47 UTC
This contradicts the UI paradigm used everywhere else. It would be even more confusing if it did not follow the single/double click behavior configured elsewhere.

A usability improvement here would be if the dialog box itself asked you for overwrite, rather than closing and passing that off to the parent app. Marking as a duplicate of the bug tracking that.

*** This bug has been marked as a duplicate of bug 146806 ***
Comment 2 Nate Graham 2018-04-11 20:45:36 UTC

*** This bug has been marked as a duplicate of bug 102972 ***