[Bug 21856] New: VB6 modal form appears BEHIND parent (borderless) form when focus is on certain controls, making parent form unusable.

http://bugs.winehq.org/show_bug.cgi?id=21856

Summary: VB6 modal form appears BEHIND parent (borderless) form
                    when focus is on certain controls, making parent form
                    unusable.
           Product: Wine
           Version: 1.1.38
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=26460)
 --> (http://bugs.winehq.org/attachment.cgi?id=26460)
VB6 project + binary to reproduce bug -- requires Microsoft Windows Common
Controls 6.0 to run and compile

In Visual Basic 6, calling FORMNAME.show 1 (open modal form) from a borderless
form, will make the new MODAL form pop UNDER the parent form when the SHOW
method is called while focus is on certain controls, but will correctly pop
OVER the parent form when focus is on other controls.

I.E.: In my BORDERLESS parent form (FORM1), I have a ListView and a
CommandButton. If I give focus to the ListView and call FORM2.SHOW 1, FORM2
pops up OVER FORM1, which is correct.
If I give focus to the CommandButton and call FORM2.SHOW 1, FORM2 pops UNDER
FORM1. This will make FORM1 unusable until you move/minimize FORM1 to find
FORM2 and close it.

This problem is particularly annoying when FORM1 is an MDI Child, since FORM2
will not show in the task bar, and it will be difficult to find FORM2 to close
it.

My findings:
- Seems to be related to Microsoft Windows Common Controls, or maybe even the
presence of ListViews on the form in particular.
- Setting FORM2's StartUpPosition property to something other than 0 (Manual)
seems to fix it (need more testing though).
- Forms with borders seem to work fine (did not test it enough)
- Which focused control will trigger the bug and which won't varies. I've had
the bug appear when focused over textboxes, commandbuttons, listviews,
checkboxes, etc.

See attached VB6 project (binary and instructions to reproduce bug included -
requires Microsoft Windows Common Controls 6.0 to run and compile).