"Is there any reason why you would want to do this?" For example, if I want to use a certain player to play video files (and most everyone probably wants to use the same player for all video types avi, mpeg etc etc). But to change the default player, the user must go to each video type and configure the default separately. The same is true for music types (mp3, ogg, etc). Groups of files types allow easier and quicker configuration and are more intuitive to the user...
"but you are the very first person who even thought about grouping." Grouping is allowed/enabled right now so somebody coded it in, but it just doesn't function for those file types that can't be removed because even after the file type is added to a group, the non-removable one overrides the one in the group. I guess if certain mimetypes must be present, there is not necessarily an easy solution to this (as I thought there might be.) I guess the easiest thing that would help is if user configured settings/groups overroad those that cannot be removed, instead of vice versa. But even then users could find confusion, when changing a setting for a file type didn't successfully change the actual program opening it...although this problem is present as long as duplicate file associations are allowed (which they are right now...). -- some file associations cannot configured/removed, prevents grouping of file association patterns https://bugs.launchpad.net/bugs/256207 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
