happily, after dancing with this for many years, I have resolved my bug. As in most cases, it was a series of cascading failures, but ultimately, it came down to an arcane threading issue in COM.
Of course, the error message was "failed to load control, is it properly registered?" which had nothing to do with the real problem.
Happy to have this monkey off my back.
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
error LNK2019: unresolved external symbol __imp_DwmExtendFrameIntoClientArea
referencing this API
I did include in my VS property pages Linker->general-> input dwmapi.lib tried to open it (the dwmapi.lib) with depedency Walker got no DOS or PE signature. I opened dwmapi.dll from windows\system32 and saw the API thru dependency walker inluded dwmapi.h in the source. The Doc has Dwmapi with a capitol D but both .lib and the dll had small d
It sounds like you are trying to write in the title bar of the window - is that right? The easy way is to call SetWindowText() on the dialog box HWND (or do whatever the MFC equivalent is) and let the default dialog proc handle drawing your text.
Otherwise you would have to draw in the non-client area, which has its own WM_NCPAINT message to handle.
thanks I choose the later NC_CLIENT might I ask you a few follow up questions 1) is there a way to determine the NC area,like GetWindowNCRect. In Additon TextOut is giving me issues would I be better off using DrawText would it need to be preceded by DrawCaption
Not sure as
if you could steer me the right direction would appreciate it
First you are a person which has specific access to the file system.
Your application is not you. The access it has depends on how it runs.
You as a person are likely checking the access but that does not mean the application has it.
Second the directories also determine access.
You can programmatically request information about permissions. Write some code that returns that information from EACH level of the directory tree including the drive letter. Then inspect that.
I`m trying to get a better understanding of how debugging works with programs build in an IDE. I have a guess on how it works but I`m hopping someone will confirm my guesses. So my guess is that the program your building it hooked through its update function (the function through which it gets updated by windows). When your run your program in debug mode the changes taking place inside your program are exchanged through the program update function as parameters with Windows which in its turn sends the data to the IDE.
A Debug version of a program includes information that an external program (the debugger) can read, in order to identify which actual statement is being executed at any point in time. The debugger captures the execution at the beginning of the program or at any specified breakpoints, and can then execute or skip instructions as directed by the user. The debugger can be run from within the IDE, or stand-alone in a terminal window, depending on the system and framework in use. When run in the IDE it is just using the IDE Windows to display information.
Last Visit: 31-Dec-99 19:00 Last Update: 31-Jan-23 17:57