It does not fix the issue on a permanent basis nor does it fix the issue for other users. But the single user can fix it _instantly_ himself without having to read the .desktop file specification. And I think that is an actual advantage. An alternative would be to create an application to write .desktop files (a bunch of entries with suggestions), probably "linked" from the application chooser dialog - that would be a viable solution, but on the other hand side, this is more nasty for the end-user.
Best 2013/4/8 Matthias Clasen <matthias.cla...@gmail.com> > On Mon, Apr 8, 2013 at 7:48 AM, Bernhard Schuster > <schuster.bernh...@googlemail.com> wrote: > > There will always be the case that some application will not do it > properly. > > Instead of annoying the end-user, give him/her the option to fix it > > him/herself. It is not that it would hurt, it's rather a salvation for > the > > daily highcups and struggle with beta/commercial applications. > > But selecting 'custom command' doesn't fix it in any way. Fixing it > would involved editing the desktop file, adding the necessary mime > type, and sending a patch to the application author. > > I don't doubt that 'custom command' functionality is useful. But I > don't think it should live in the app chooser dialog. >
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
