79535793

Date: 2025-03-26 08:30:02
Score: 1.5
Natty:
Report link

"You let the call go to base.WndProc which is going to set its own Result" Genius! That is the solution! Whoa, thanks Raymon Chen!

Thus with other words... When I handled the message in the overridden WndProc I can set the Result to a number and not call the base.WndProc. For messages not handled I call the base WndProc. Be aware that the return number has to be in a range that is not system-defined (https://learn.microsoft.com/en-us/windows/win32/winmsg/about-messages-and-message-queues#application-defined-messages) so 0x8000 to 0xBFFF works.

Thanks again!

Reasons:
  • Blacklisted phrase (0.5): thanks
  • Blacklisted phrase (0.5): Thanks
  • Has code block (-0.5):
  • Low reputation (1):
Posted by: Jens Malmgren