GNOME Bugzilla – Bug 342952
"Open File" Dialog doesn't respond when folder and files are selected
Last modified: 2018-02-12 17:46:13 UTC
From http://launchpad.net/bugs/46626 To reproduce: 1. Open gedit, or any program that uses the standard Gnome Open File dialog. 2. Select a file and a folder, so that both are shaded orange. 3. Click on the "Open" button. Nothing happens. There should be a pop-up dialog that says "Please select files only" or something like that. Other information:
I probably should file a separate bug about this, but there are issues with selection handling when you are in select-multiple-files mode. - Open a multiple-files file selector (evolution insert-attachment say) in a directory with subdirectories. (The first subdirectory will be selected) - Hit C-L and type the name of a file *in that directory* - Hit return to close the C-L dialog - Both the directory *and* the file will be selected. (But if the file is off the first screen, you don't see it is selected) I don't know if this happens with the 2.9.x inline location bar, but it makes me think (getting back to the subject of this bug report) that in select-multiple-files mode the treeview selection should be adjusted / hacked up so that you can select - One folder - *Or* multiple files But if you have a folder selected and try to Control-click a file, it should deselect the folder, and if you have multiple files selected and Control-click a folder, it should do nothing. (I think do nothing is better than unselecting the files)
Why is this still not confirmed!? I myself can reproduce this every single time!
Owen's idea from comment #1 is pretty good. We should be able to hack the selection handler to unselect folders as appropriate.
Does this suggested select-policy mean, that one would have to move files and folder separately on after the other? This would be another annoying restriction and one should be able to turn it off.
I mostly agree with Owen's suggestion in #1 but I think the "do nothing" option should apply to all cases , not selectively. I see no justification of treating the two cases differently , this will be confusing. Such hidden iffing and butting is only apparent to those who work on the code. The user interface must be consistent in its behaviour. I also think there is a need to indicate that the files cannot be selected with a directory and vice versa. Simply doing nothing in response to a user action that would normally produce a result is again confusing and will give the impression of buggy behaviour. Since it should only be necessary to point out what is happening once, a clear error message would probably be the best solution.
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it.
reproducible on Arch Linux, gtk3 3.22.26+161+g60750b3ffd-1.