Comment 7 for bug 1023840

Basically, I would say that - yes - qpdfview behaves as a unique application by default now. But since manipulating the launcher file is more or less trivial and works for most desktop environments, I'd say this is a rather weak default, so now work style is really discouraged.

As several people asked for it and some people told me that changing the launcher was the first thing they did, I would try to ship it that way for next version and wait for the possible backlash. If there is substantial frustration, it can always be changed back.

(I also agree that activating windows is the job of the window manager and it is the one who actually does it. qpdfview just tells the window manager that something is happing that might need attention but the window manager might choose to ignore that. (If we don't do that, the window manager would not be able to know that the command just executed had any consequence whatsoever in another window.))