From: Matthew W. O. <wei...@gr...> - 2003-02-19 14:23:55
|
-- Ernst De Ridder <hnr...@in...> wrote (on Wednesday, 19 February 2003, 01:22 PM +0100): > > When in rox 1.3.6 file A is selected and the users presses the menu > button over file C, the menu actually applies to the selection, i.e. to > file A. I find this confusing and it already has caused me to delete the > wrong file:-( I would expect one of the following: I've had similar problems, nothing yet with deleting, but the same process. > a) The selection is cleared when clicking menu over C. This will cause C to > be the temporary selection for the duration of the command, afterwards the > selection stays cleared. > > b) The selection is left as-is and the menu applies to file C. This might be > the easiest to explain, but has the disadvantage the C is not visually > marked. > > c) The selection is changed to file C and the menu applies to file C. When the > menu pops down again the selection (A) is restored. This might be the most > convenient to the user, and I think it's also the easiest to program. I like (c) -- but I also like the fact that I can select a bunch of files, click anywhere, and have the action apply to them. What I don't like is having *one* file selected, right-clicking on another, and having the menu be for the selected file. Maybe (c) if only one file is selected, otherwise the regular behaviour is multiple files are selected? -- Matthew Weier O'Phinney ma...@we... |