> Hi Arto,
>
> Thanks very much for your reply.
>
> I've been proceeding to develop with the presenter only in fullscreen,
> exclusive mode and have had some success without switching between non- and
> windowed modes. I find the terminology really confusing since there seems to
> be at least 2 other uses of "exclusive mode" in the DirectX canon - one for
> input devices and one for DirectDraw surfaces. For my own disambiguation,
> I've been thinking in terms of windowed and non-windowed Direct3D devices.
>
> I've discovered that if my WndProc claims to handle WM_NCACTIVATE messages,
> then my app doesn't get minimized "behind my back" and I can effectively
> debug in a 2 monitor system. Apparently someone hooks my app window and does
> stuff when it loses focus through this message. I'm guessing that this
> happens inside IDirect3D9::CreateDevice. This 'cheat' seems to keep me from
> getting a device-lost return from IDirect3DDevice9::Present, too. I'm pretty
> nervous about leaving this in a release build, though, since I don't know
> what else might be going on. I'd love to know the whole story, but I haven't
> been able to dig it out of any dox.
>
> I still have funny stuff going on with ::ShowWindow(..). Seems like I can
> show and hide OK, but if my app is still 'presenting' when the window isn't
> visible it shows on the monitor anyway. I suspect this may be result of my
> WM_NCACTIVATE preemption and that I'll be able to hack around it by checking
> the window visibility before I do any rendering.
>
> But it might be something else, too - I'd be curious to know what COM
> interfaces you needed to muck with, Arto, in switching between windowed mode
> and non-, just to see if anything sounds suspicious.
>
> A little off-topic, but here's a nugget that might save someone an hour or
> two of hair-pulling: the order of monitors you get from EnumDisplayMonitors
> and IDirect3D::GetAdapterMonitor is not necessarily the same. The former
> seems to return monitors in left-to-right desktop order while the latter
> always returns the primary display as adapter 0. Easy to miss the
> distinction if your primary is always on the left.