https://bugs.winehq.org/show_bug.cgi?id=34631
--- Comment #34 from 399989567@qq.com --- (In reply to 399989567 from comment #33)
(In reply to Zeb Figura from comment #31)
*** Bug 53772 has been marked as a duplicate of this bug. ***
I would like to ask what is the reason for judging whether a window is added to the window manager in wine. For example, in the is_window_manger function of winex11.drv, I see that the child window in wine does not need to be added to the window manager, and the full-screen window needs to be added to the window manager.
====================
I would like to ask what is the basis for judging whether a window is added to the window manager? I'm not asking the code logic for the judging in wine, I'm asking why the code be coding like that? If we judging a window need to be add to the window manager,What is the basis we follow?
such as : We know that the child window is managed by its parent window,
so there is no need to join the window management.
====================
Because I think a visible POPUP window (WS_VISIBLE) in the screen should be added to the window pipe, but I want to know "the basis for judging whether a window is added to the window pipe", and then judge whether my logic is correct.
If my logic is correct then this bug will be fixed.
I refuted myself, adding the shadow window to the window manager can indeed solve the problem, and the shadow window will not be displayed on the top layer, but such modification will cause new problems, so there should be a corresponding reason that wine did not do this in the design. consideration (although I still don't know what kind of consideration)
I will still be here for getting the basis for judging whether a window is added to the window manager.