[Bug 43765] New: RSpec-Explorer windows are sometimes unresponsive to keyboard and mouse input

https://bugs.winehq.org/show_bug.cgi?id=43765

Bug ID: 43765
           Summary: RSpec-Explorer windows are sometimes unresponsive to
                    keyboard and mouse input
           Product: Wine
           Version: 2.17
          Hardware: x86
               URL: https://www.rspec-astro.com/setupdownload/
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Under some conditions, the application will refuse to respond to mouse and
keyboard input. The windows can be minimized, closed, focused, etc; and edit
controls will blink the caret, but buttons won't be clicked and other controls
similarly won't update. This affects not only the main window but also the
common open-file dialog.

I can pretty reliably trigger this by starting the main application, ensuring
that it is not maximized, then clicking the folder icon in the upper left to
trigger the open-file dialog. Said dialog will in most cases not respond to
input as described above; and, when it is closed, the main window will
sometimes similarly stop responding to input. I can also see this behaviour,
though less consistently, with the first window that shows up (warning you that
this program is a free trial); this window sometimes fails to respond to input,
and usually the main window will fail to respond after it is closed.

This state of unresponsiveness can in fact be undone. If the main window is
unresponsive, minimizing and restoring it will cause it to again be responsive.
More bizarrely, if one of the dialog windows is unresponsive, moving the main
window below the dialog (or nearly below it) will cause it to be responsive;
additionally, any keyboard or mouse events will be processed.

Adding some traces to DIALOG_DoDialogBox() shows that there are clearly mouse
events in the queue, but they seem to be ignored by PeekMessage(). I have no
idea why this would happen.