id summary reporter owner description type status priority component version resolution keywords cc game 7715 GUI: Improve Mass Add button criezy Mataniko "{{{#!Markdown Currently the Mass Add button is really not obvious. Without documentation you have no way o know it is there. I have a few suggestion to improve the situation: 1\) There is no need to differentiate ""Add Game"" and ""Mass Add"" button. Just use one ""Add Games"" button \(note the plural\). The idea there is that for most users this is basically the same thing: you select a directory and the game\(s\) in that directory are added. The only difference is that ""Add Game"" has some constraints, namely it adds only one game and it doesn't look in sub directories. It might be different from a developer point of view, but I am not convinced it should for a user. If you use Mass Add and select a directory where you have one game it behaves more or less in the same way as ""Add Game"". 2\) Use two separates button. But I don't like this idea \(there are already too many buttons for my taste in the launcher\). 3\) Add a small downward array \(for a popup menu\) on the right of the button. When clicking on that part of the button you get a popup menu with ""Add one Game"" and ""Add several games"" and if you click on the left part of the button it behaves like the ""Add Game"" button. I am not too fond of that solution either. For one thing the popup menu arrow is usually seen on toolbar button and not on action buttons. This might not be understood by everybody. Also the area on which to click to get the contextual menu is mall, which goes against usability rules \(and might be an issue on some platforms\). 4\) Use just one button ""Add Game\(s\)"" and add an option \(check box ""Add all games from the selected directory and sub-directories""\) in the file selection dialog \(which might be an issue on platforms on which the native file selection dialog is used\). }}} {{{#!div style=""font-size: 75%"" Ticket imported from: !#2821504. Ticket imported from: feature-requests/531. }}}" feature request closed normal GUI fixed