- Thread starter
- #61
WM_GETMINMAXINFO is coming in way too late in your scenario. Could you please log the window messages as well, so I can see if there is a better point beside relying on a following WM_GETMINMAXINFO.Log attached with the correctly working MP. First turn off/on TV. Then turn off /on receiver.
Would like to avoid a hardcoded delay after a WM_DIPLAYCHANGE, even though some thread.sleep() of 1-2 seconds will work in all scenearios. Just don't like such hardcoded stuff. I prefer getting something from Window to tell me it's ready.