If you really want to do it through direct handling of
and then cancel closing, look at the message description:
As you can see, the message does not have parameters except message ID, so you don't have any information on the cause of the message.
If you wanted to prevent closing unconditionally, you would need in
message handler, you would need to return TRUE from
without calling the
function, but if you need to do it on the condition related to the source of the message, you don't receive anything which gives you a clue.
You should do some work-around. Insider the application, devise a custom message like "WM_USER_CLOSING", send it inside the application process, handle it, and actually close the window or not, depending on the user's decision. It won't affect a handling of the message
sent from external application, just as you wanted. But — please see my comment to the question; probably you can create better application design instead.