[dragonplayer] [Bug 459326] New: UX bug - "play file" dialog uses inonvenient default for "Files of type" input
Alex Kh
bugzilla_noreply at kde.org
Sun Sep 18 13:42:44 BST 2022
https://bugs.kde.org/show_bug.cgi?id=459326
Bug ID: 459326
Summary: UX bug - "play file" dialog uses inonvenient default
for "Files of type" input
Classification: Unclassified
Product: dragonplayer
Version: 22.08.1
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: khalukhin at gmail.com
CC: myriam at kde.org, sitter at kde.org
Target Milestone: ---
If you ever attempted to open a media file with using "Play file" button in
Dragon player, it opens up a file picking dialog, with the value for "Files of
type" input control filled with (just assuming) whatever first supported file
format your player has been compiled with. For me it's "MXF video (*.mxf)".
This makes it hard for users to use this dialog at all, because they need to
know it in advance what kind of file they're about to open and set that filter
first. Wast majority of regular users don't have an idea about these kind of
technical detals, like video file format differences, all they want is to
playback a file - either audio or video.
What it should be instead - a very first item in that "Files of type" control
should be something like "All supported media formats", which should be a
superposition of all file extensions this particular instance of Dragon player
could handle. E.g. *.avi, *.mp4, *.mpg ...
If some advanced user still wants to change this dialog to see only files of
specific format, he would be able to do that, bu changing that default "All
supported media format" option to something of his choice.
Also, the list of possible file types should be displayed as sorted one,
currently it's unsorted and it makes this kind of selection difficult.
The behavior is observed whike using dragon player compiled out of the latest
sources with kdesrc-build, so I set the affected version to the most recent
stable release. The same behavior was existing for the version 20.12.0, the one
I have in Debian 11 Stable
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list