|
Hi
I got a link error
error LNK2019: unresolved external symbol __imp_DwmExtendFrameIntoClientArea referencing this API
DwmExtendFrameIntoClientArea
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
Any help appreciated thanks
|
|
|
|
|
|
Richard I changed it in the release Property Pages added dwmapi.lib but I did a debug build
got a clean link now
thanks
|
|
|
|
|
Oh yes, yet another one of Microsoft's 'Easter Eggs' left for us to trip over.
|
|
|
|
|
Hi I am trying to write a caption to my modeless dialog box I did a getwindowrect and screen to client as the negative "y" coordinates would be where I would want to place my text
did dc->Setcolor to blue got my text extents from CDC When I did a dc->textout nothing happened
I also noticed Cwnd has DrawCaption but doesnt take a parameter for Text. DrawText however has a DT_TEXT flag but where does it pick up the text
Can you write a caption using a device context
Thanks
|
|
|
|
|
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
|
|
|
|
|
WriteFile return access denied?
while i providing admin privileges
please help me for this.
HANDLE hCD = CreateFile (file_Name, GENERIC_READ|GENERIC_WRITE,
FILE_SHARE_READ|FILE_SHARE_WRITE,
NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL,
NULL);
WriteFile (hCD, Buffer, Size, &bytesWritten, NULL);
its fails with access denied.
thanks in advance.
|
|
|
|
|
Check the file name and make sure that it is where you think it is, and is not protected against write access.
|
|
|
|
|
i chk all is ok n its not write protected at all....
now what can i do
|
|
|
|
|
Sorry, it is impossible to tell what may be the problem without access to your system.
|
|
|
|
|
I just tried your actual code on my system and it works fine, so the problem must definitely be something to do with the file or its location.
|
|
|
|
|
its my card storage connected on usb 3.0 port
on usb 2.0 its working fine
|
|
|
|
|
You need to check in Settings to make sure it is accessible. You can try a simple copy from File Explorer as a start.
|
|
|
|
|
Two things
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 have a very simple project that I am converting from VS2015 to VS2019. The project "converts" successfully but will not compile due to:
"fatal error C1189: #error: MFC does not support NTDDI_VERSION less than NTDDI_WINXP. Please change the definition of NTDDI_VERSION in your project properties or precompiled header."
I've turned off precompiled headers and added to my stdafx.h the following line:
#define NTDDI_VERSION 0x0A00
I've also tried
#define NTDDI_VERSION _WIN32_WINNT_WIN10
stdafx.cpp will not compile. So, my question stands - is there a method to determine all of the project macro settings?
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Solved - ignore all of the online garbage.
create a dummy VS2019 application. There you will see that Microsoft has migrated to using targetver.h which includes:
#include <sdkddkver.h>
That's the secret.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Hi Charlie,
Good to see that you fixed your issue. Just in case the search engines index this question I wanted to add that you can use the /P compiler option[^] to dump the preprocessor to file.
Best Wishes,
-David Delaune
|
|
|
|
|
Thanks for that tip. Exactly what I was looking for.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Hello, I'm a begginer in Golang and I need a good IDE for my exercises. Anyone can help me with a good IDE and how to install? Thank you very much.
|
|
|
|
|
|
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.
|
|
|
|
|
So basically the program being debugged is a sitting duck residing in the memory that an external program can read at will/without any formalities.
|
|
|
|
|
Not at all, since you, the user, are in control of the system and what application are running and what they are allowed to do. And Debug information is not a simple text file that anyone can immediately interpret.
|
|
|
|