C / C++ / MFC

Do you work for Boeing? The Master said, 'Am I indeed possessed of knowledge? I am not knowing. But if a mean person, who appears quite empty-like, ask anything of me, I set it forth from one end to the other, and exhaust it.' ― Confucian Analects

Nice. :thumbsup:

You don't have privilege to run it. Log in or run the program as administrator. In vino veritas

I believe that too.A lot of things have happened in so many years and likely that's not a very good combination in this case, specially when it comes to Windows and its sometimes "very tricky" registry. I've tried three different tutorials (unfortunately all of them very old too) and I got the same result at the same point and the same function, so maybe there is something I have to fix behind the scenes of the new Windows 10 registry and well, I'll -try to- work on it. Don't feel sorry for yourself, I really appreciate your input: we can't have all the answers :-D TY Stefan_Lang :thumbsup:

Do your standard apt-get update and install on libc somethings missing. In vino veritas

Hi Victor, I've been meaning to tell you that I am happy to see you have finally moved over here from CodeGuru. I followed Chris over to his new site some 18+ years ago soon after Zafir Anjum sold codeguru and I rarely go back to the old site anymore. Victor Nijegorodov wrote: Why do you need the UpdateData at all? There was a great essay about Avoid UpdateData of Joe Newcomer. I'd recommend you to check it out! Actually in this case he may need to call UpdateData() because he is bypassing both the CWnd::OnOk and also exiting the dialog with EndDialog(SOME_RADIO_ID); With that knowledge go and read the final two paragraphs in the debate between Doug Harrison and Dr. Newcomer. If we are going to suggest that the poster "ForNow" avoid using UpdateData() then we need to ensure that he is using control variables. Best Wishes, -David Delaune P.S. I haven't used MFC in nearly 10 years, not sure why I even remember these things.

I just used a console application to set the hook, which will inject the dll with the callback. I'm getting a valid handle and the hook is executed in the address space of the target application. There are no messages to or from the console application. I'm not trying to spy anything on a console window. Maybe that was not clear. I get a "CWPSTRUCT" with the right message code and I have trouble to convert the message/pointer to a string and write it to a file. All of this is done in the dll. I don't know, how to setup the debugger to stop inside the dll. It's more like a try and error at the moment and that can be frustrating. I don't see this as a waste of time, because I'm also learning. I appreciate your time and help! Thank you!

Nowadays it's not nearly as bad as it used to be. The biggest culprit was and still is the UI, and in fact any graphics or sound functionality, simply because there are no C++ standard libraries for that. However, there are OS independend libraries around for that purpose. Everything that is in the C++ standard libraries, including STL and BOOST, should work out of the box on any OS without changing the code, unless the compiler you're using is not adhering to the standard (in which case you should consult your compilers compatibility documentation). GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

Well, that really does not explain what is happening. Perhaps if you showed (in your original question) the actual code and the values that cause the problem ...

Well it always worked as I described for me. But I admit I haven't heard of the canonical mode before, so I'm going to trust you on this. GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

That's what I am doing. :thumbsup: Thanks. I'd rather be phishing!

The strange thing was that using both the debugger and Spy++, I could not 'see' the multiple messages coming in. In both cases after a scroll gesture on the touchpad, they both showed just one message and then went back to the application window. So it as if the delta values were just too small. BTW, thanks for your interest.

_Flaviu wrote: The strange thing is that this behaviour is present on some PC, and on some PC are not present Because, as I explained, there is an association on the PC, each PC, which specifies what if anything to open the file with based on the extension.

Yes, but you need to do all the drawing of the frame and title bar. Take a look at WM_NCPAINT message - Windows applications | Microsoft Docs[^].

Well, it was more than six years back... I used the [NSSM - the Non-Sucking Service Manager](https://nssm.cc/description) The most important thing is you could used the original UI application to use with..., however, in "service" mode you must forbid all UI features.

I was begging to think no one here was thinking. Thanks INTP "Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra "I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone

Thank you very much for your support!