|
|
This is intentional, and I think makes sense in these contexts. i.e. in Explorer, checkbox and selection is one and the same. In auto-tag, organize, etc. the checkbox determines whether the dialog's action is applied to the track, whereas selection allows _other_ actions to be taken on the track. It's true that this means that Shift-select doesn't work, but in general, I think that the current approach is preferable since users may want to listen to or view Properties of tracks in the dialog. |
|
|
I my opinion, if someone selects files in the main filelist and opens some of these dialog boxes, his intention is not to start playing any of these tracks, or to analyze their volume or any other action that is available in the context menu, but to do the action that is intended with such dialog box. The only possible action that could be wanted is to view Properties, but that could be done by enabling the needed column in the listview. Did you ever use any of these options inside these dialog boxes? On the other side, the current implementation makes checking / unchecking range of files tremendously difficult. Could you imagine that you need to uncheck e.g 100 files, ticking one by one? |
|
|
Example of how this can be useful: - User is auto-tagging a file and wants to hear what version of the file is being edited. |
|
|
If that is the whole reason for the current behavior, you don't need the selection mode at all. I think it is highly unlikely that you would want to select multiple files in such dialog and start their playing all at once. Maybe it would be better if you add a play button to the hovering row (and maybe a menu button), which would do the same thing, similarly as you have in popups. In that case, you could have the same behavior of selecting/checking files as in Explorer, and a possibility to start playing of a hovered file. Play and menu buttons in popups.png (17,456 bytes) |
- Anonymous
