Re: Very annoying problem

On Thursday, 28 March 2019 11:34:33 IST René J.  V. Bertin wrote:
> Leon Pollak wrote:
> So what actually happens is that whenever you switch to debug mode a window
> may start popping up at a 3-5 minute interval which never shows its own
> content (showing its backdrop instead)?
My type error: 2-3 seconds after switching to debug mode.
I am not sure that what is shown is background of the window.
It looks like something transparent - it displays what was in this place before 
I switch to the debug window or return to the kdevelop (if I switch to mc, for 
example).
If I simply switch to the debug mode, it shows the part of the build pane.
If in this state I switch to another application and then return - it shows the 
corresponding part of the window I returned from.


> Could this be a misbehaving kioslave which tries to pretend to be one of
> KDevelop's windows (using setTransientXXX or some similar call)?
Ou! It is too complicated for me - I am dumb in Qt...:-)
I am embedded programmer...



> I understand you can in fact interact with its borders; what happens when
> you click somewhere inside this "invisible" window? Seemingly nothing,
> correct?
Yes, nothing happens. That's why I discovered the borders so late.


 
> If so, you could simply use the old xwininfo tool to obtain some information
> about the window. I cannot tell you off the top of my head how to obtain
> process information from there but maybe someone else can tell you that.
Thank you, Rene. I will do this xwininfo - already studied how to use it.
You will laugh at me, but just at the moment when I wanted to do xwininfo, the 
effect disappeared!
This was already happening to me and I was so glad - I could continue to 
work...:-)
Now I am angry - wanted to check the window owner and can't...:-)
I will return when the issue will return.

THANKS!!!
-- 
Leon