0

I'm working with common dialog recently and I've found that a hWndOwner is required in the structure that passed to functions like ChooseColor.

It seems of no difference when I used different hWndOwner. What does different hWndOwner choosing affects? Are there anything to take care when choosing the owner window?

ksyx
  • 41
  • 1
  • 9
  • Are you looking for this: https://learn.microsoft.com/en-us/windows/win32/winmsg/window-features#owned-windows – Simon Mourier Apr 11 '20 at 09:24
  • answer yourself, and gain some points – Simon Mourier Apr 11 '20 at 09:26
  • See [owned windows](https://learn.microsoft.com/en-us/windows/win32/winmsg/window-features#owned-windows) to learn, why passing an owner is useful. – IInspectable Apr 11 '20 at 09:55
  • [Raymond Chen's blog](https://devblogs.microsoft.com/oldnewthing/) has a [series of articles on how window modality works](https://devblogs.microsoft.com/oldnewthing/?s=Modality), particularly in relation to dialog window owners. – Remy Lebeau Apr 11 '20 at 10:13

1 Answers1

0

Thanks for all who commented! Below are the key ideas I've got from the document.

  • There are a few things that relates to ownership, as taken from the document:

    • An owned window is always above its owner in the z-order.
    • The system automatically destroys an owned window when its owner is destroyed.
    • An owned window is hidden when its owner is minimized.

  • Setting owner to a child window (a window that is not a overlapped window or popup window) is equivalent to setting it to the top-level parent window.

  • The ownership could not be transferred after the window is created.

That's what I've learnt by reading the document. It would be much better if someone can give some extra information that is not included in the document.

ksyx
  • 41
  • 1
  • 9