[Bug 170979] strange behaviour in "save as" dialog

[Aaron Peterson]

http://bugs.kde.org/show_bug.cgi?id=170979


Aaron Peterson alpeterson gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alpeterson at gmail.com




--- Comment #11 from Aaron Peterson <alpeterson gmail com>  2008-09-28 07:46:17 ---
Expected behavior in save as dialog:

doubleclick on folder, chdir to that folder
singleclick on folder, select the folder, (can do rename or other normal file
manager tasks)

doubleclick on file - replace the text in the filename for the saveas with the
filename.
single click on a file -- select the file (Does not change the save as filename
text)

Click save button with a filename that already exists:
        prompt: would you like to overwrite this file? yes / [No]   No default
                if no selected, go back to save as dialog.
                if yes is selected save and close the save/save as dialog.

click save button with a nonexistant filename, save and close.


Note, for systems with the single click as default, doubleclick can be replaced
with another "catproof" method to select action.

(note, the way I see it is there are "catproof" and "hair trigger" selection
methods...  doubleclick is an example of catproof, and single click is close to
a hair trigger (depending on how still your mouse has to be before the system
recognizes an action)

So in a single click environment, I  a plain single click should still not nuke
the filename I carefully typed in the field.  I would expect a dialog, or
better yet an unobtrusive message expanded into the save-as dialog like the IE
/ Firefox web browsers have less obtrusive messages expand in the content
wrapper.

Single Click could be the best, but the single click only systems without
catproofing will cause severe loss of work.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.