Search:

Thanks for the quick responses. I'll have to agree with you, it appears that this is as far as I'm going to get as far as digging into the core of the issue. It sounds like we all coming to the same,...

Thanks for the quick responses. I'll have to agree with you, it appears that this is as far as I'm going to get as far as digging into the core of the issue. It sounds like we all coming to the same,...

Normally I would agree with you, but I believe I have simplified the case enough to rule that out. I think it has more to do with how the messages are being triggered, if I run this in debug, I think...

UPDATE: I've removed the AfxMessageBox calls, and replaced them with file writes (TRACE wouldn't work because this problem doesn't manifest in debug). This appears to have made the behavior I was...

It sure does, doesn't it!

Arjay's alternative makes sense, so saying that using a worker thread wouldn't help the issue was incorrect on my part. If it was implemented that way, then the...

I'm not scared of implementing a worker thread. I'd prefer it, most of my issue here is that this code is part of a 10+ year old project that is being maintained, and the larger the change, the...

Thanks for the response Igor. What you are describing is what I believed is happening as well, I just couldn't find any documentation or forum posts to confirm it. Is this just an observation of...

I have a bit of an odd issue. I maintain a piece of software that appears to be handling multiple calls to OnSetActive() at once.

The problem manifests when performing a large image operation....