Re: Very annoying problem

Hello, René.
Its me back with the problem which returned back... :-)
Our previous exchange I still preserved below under the "===" line.
Recently the problem permanently returns on the second-third entering  
into the debug mode.
As I said previously, i managed to lessen the problem by "resizing"  
this "window' to minimal possible size.
Now I managed to run xwininfo and here is the result:
xwininfo: Window id: 0x7200a3b "Memory ? KDevelop"

   Absolute upper-left X:  1807
   Absolute upper-left Y:  897
   Relative upper-left X:  0
   Relative upper-left Y:  0
   Width: 89
   Height: 132
   Depth: 24
   Visual: 0x130
   Visual Class: TrueColor
   Border width: 0
   Class: InputOutput
   Colormap: 0x7200a3a (not installed)
   Bit Gravity State: NorthWestGravity
   Window Gravity State: NorthWestGravity
   Backing Store State: NotUseful
   Save Under State: yes
   Map State: IsViewable
   Override Redirect State: no
   Corners:  +1807+897  -24+897  -24-51  +1807-51
   -geometry 89x132-24-51

and the screenshot is here:
https://drive.google.com/open?id=1ynks_MDjjJsRhCSetA4FA2MLcshnq2s4
You can see the traces in the right lower corner.

As I can understand, the window is some trace of the memory  
presentation window. And this sounds logic, as sometimes when I want  
to view memory and try to use it, it simply doesn't open.

Thank you!!!
===================================================================
On Thursday, 28 March 2019 17:09:14 IDT Leon Pollak wrote:

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