[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #8 from Manfred Knick  ---
(In reply to Christoph Cullmann from comment #7)
> Kate reuses existing instances.
Which is a very good habit, indeed!

> It ATM tries to reuse the "right" instance 
>   based on your current active virtual desktop.
..^^^

Not precisely: it ignores from which X11 Screen it is requested.

> kate -n will avoid that, ...
No - c.f. (comment #1) :
>
> . . . "kate --n"
> 
> do not help, as already stated in ... 

> I don't see how I can "change" kate to help your with that issue.
Evaluate the _tuple_ [ X11 Screen | virtual screen ] of requesting
in kate's initial code trying to identify 
_which_ instance of kate is running on the same X11 Screen.

Two humble questions, for example:

A) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n325   ff

// prefer the Kate instance running on the current virtual desktop

   ??? Does KWindowSystem::currentDesktop() respect Multiple X11 Screens?

B) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n334   ff

// query instance current desktop

   ??? Does QDBusConnection::sessionBus() ?
   ??? Which sessionBus() ?   Always that from Screen_0 ?

Compare  --> "B"  in
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 .


P.S.:   WONTFIX is o.k. for me ...   Thanks for answering!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Christoph Cullmann]

https://bugs.kde.org/show_bug.cgi?id=379488

Christoph Cullmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||cullm...@kde.org
 Resolution|--- |WONTFIX

--- Comment #7 from Christoph Cullmann  ---
Kate reuses existing instances.
It ATM tries to reuse the "right" instance based on your current active virtual
desktop.
kate -n will avoid that, but might not be that nice to use, as you will get a
new window on each call.
I don't see how I can "change" kate to help your with that issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #6 from Manfred Knick  ---
(In reply to Christoph Feck from comment #5)

> Since you reported it for multiple KDE applications,
.^^. ???

Sorry - I don't understand.

> are there actually KDE
> applications that work correctly?
Lots of.

> In other words, is there anything that can
> be fixed inside Kate, 
Surely. Esp., c.f. 
[ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298638157 ]

To me, the code trying to map new KDE requests to already running ones seems
broken.

> or is this a general problem with all Qt5 applications?
Definitely _not_ .

Perhaps, you might consider reading the links referenced in "Description"
above,
esp. "Overview" and "... Patterns".

Then, note the contradictory cross-check findings concerning ctwm and FVWM.

You are welcome to use PM as desired.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #5 from Christoph Feck  ---
Since you reported it for multiple KDE applications, are there actually KDE
applications that work correctly? In other words, is there anything that can be
fixed inside Kate, or is this a general problem with all Qt5 applications?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #4 from Manfred Knick  ---
Although confirmed as working stable multiple times,
unfortunately, Elv13 stated that nobody @ Awesome would care about
independent X11 screens ("ZaphoMode") any more;
c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff.

Same disinterest stated by leading upstream (=KDE) developers.

If really nobody cares besides me,
I do not mind to close as "WONTFIX".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #3 from Manfred Knick  ---
Meanwhile also verified on ctwm with 4 screens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #2 from Manfred Knick  ---
CONFIRM:
" ... awesome pretty much does the same thing as you do when you start kate
from a terminal."
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298390441

At the very end, the cross-check findings concerning "FVWM -s" in
[ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 ]
very much caught myself by suprise against all gathered expectation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

https://bugs.kde.org/show_bug.cgi?id=379488

--- Comment #1 from Manfred Knick  ---
In contrast to

. . . "konsole  --separate"

[ https://github.com/awesomeWM/awesome/issues/598#issuecomment-166920100 ] ,

. . . "kate --startanon"
. . . "kate  -s"
. . . "kate --n"

do not help, as already stated in

[ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 ] .

-- 
You are receiving this mail because:
You are watching all bug changes.