https://bugs.kde.org/show_bug.cgi?id=377199
Michael Schwarz <michi.schw...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michi.schw...@gmail.com
--- Comment #2 from Michael Schwarz <michi.schw...@gmail.com> ---
(In reply to Boudewijn Rempt from comment #1)
> That's not a bug, but a feature, requested by users. It means that newly
> opened documents go into the existing krita window, instead of in a new
> process/window. We might be adding a commandline flag to disable the
> single-application mode at some point, but that's not going to happen soon.
Thank you for your response.
I think you may have misunderstood my explanation. First of all, that use-case
does not even work. When I open one version of Kirta and then explicitly open a
document with the another version (e.g. by right-clicking and choosing Open
With > Krita [version]), the selected version of Krita just opens and closes
again, without the document getting opened in the already-open version of
Krita.
Secondly, the use-case you are describing is already solved by macOS. Each
document is associated with the bundle ID of the application it should be
opened with. If an application with that bundle ID is already open, the event
to open a document is sent to that application, otherwise the application will
be launched before sending the event. What this means is that even if I have
multiple versions installed, if one of them is already running, double-clicked
documents will be opened by that version.
Nonetheless, the issue I'm describing does not relate to how documents are
opened when multiple versions of Krita are installed. I'm talking about opening
the _application itself_. I ask you to reconsider this issue as it is a
contradiction to how applications on macOS are supposed to work (i.e. how they
work when using Core Foundation). My perception is that the answers to
questions like this will influence how well Krita will be accepted on macOS in
the long run.
--
You are receiving this mail because:
You are watching all bug changes.
