C / C++ / MFC

Re: Looking for advice/guidance on writting / painting to non Client area of window

30-Dec-21 11:54

Make sure you are using the correct DC. Windows loves to clip stuff when drawing.

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.

RedDk30-Dec-21 7:29

RedDk

30-Dec-21 7:29

I did a quick searchereno using what we use, Lucene.net, and it's query syntax, and obtained:

XFontDialog - Customizing CFontDialog Part I: Adding Font Filters[^]

If you scroll down to the end of the page where the last image is perfunctorily displayed perhaps you'll see what I saw and think Is this what a non-client area customization looks like?

Re: Looking for advice/guidance on writting / painting to non Client area of window

ForNow30-Dec-21 7:50

ActiveX control development - old farts need apply

30-Dec-21 7:50

thanks will look

charlieg28-Dec-21 16:08

Re: ActiveX control development - old farts need apply

28-Dec-21 16:08

No offense to you youngsters...

I'm looking for someone or people who have scars from activeX development. Yes, I know it's obsolete, but unknown to most of you the world runs on existing code.
Rather than pollute the forum, you can find me at cgilley2640@gmail.com.

This is a cash opportunity - I'm stuck. Email me and I'll give you the particulars.

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.

Richard MacCutchan28-Dec-21 22:21

Re: ActiveX control development - old farts need apply

28-Dec-21 22:21

Why is this in the C/C++ forum rather than Collaboration / Beta Testing Discussion Boards[^] ?

charlieg29-Dec-21 1:37

Re: ActiveX control development - old farts need apply

29-Dec-21 1:37

Because it's all written in C++? Smile | :)

I'll move it.

Also, I did not realize the discussion board list had multiple levels. Just learned something new.

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.

charlieg29-Dec-21 16:49

Link error referencing Windows Desk Top Manager

29-Dec-21 16:49

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.

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.

ForNow28-Dec-21 1:35

Re: Link error referencing Windows Desk Top Manager

28-Dec-21 1:35

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 MacCutchan28-Dec-21 2:03

Re: Link error referencing Windows Desk Top Manager stupid me

28-Dec-21 2:03

According to the documentation at DwmExtendFrameIntoClientArea function (dwmapi.h) - Win32 apps | Microsoft Docs[^], the library is named Dwmapi.lib. However, my experiences is that the linker does not care about character case in .lib names. There must be something else that prevents it from satisfying this reference.

ForNow28-Dec-21 2:45

Re: Link error referencing Windows Desk Top Manager stupid me

28-Dec-21 2:45

Richard I changed it in the release Property Pages added dwmapi.lib but I did a debug build

Frown | :(

got a clean link now

thanks

Richard MacCutchan28-Dec-21 3:38

Drawing a Caption using CDC Class

28-Dec-21 3:38

Oh yes, yet another one of Microsoft's 'Easter Eggs' left for us to trip over.

ForNow24-Dec-21 3:32

Re: Drawing a Caption using CDC Class

24-Dec-21 3:32

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

Graham Breach24-Dec-21 7:08

Graham Breach

24-Dec-21 7:08

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.

Re: Drawing a Caption using CDC Class

ForNow24-Dec-21 7:35

WriteFile return access denied?

24-Dec-21 7:35

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

Le@rner20-Dec-21 21:32

Le@rner

20-Dec-21 21:32

WriteFile return access denied?

while i providing admin privileges

please help me for this.

C++

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.

Richard MacCutchan20-Dec-21 21:51

20-Dec-21 21:51

Check the file name and make sure that it is where you think it is, and is not protected against write access.

Le@rner20-Dec-21 23:33

Le@rner

20-Dec-21 23:33

i chk all is ok n its not write protected at all....

now what can i do

Richard MacCutchan20-Dec-21 23:50

20-Dec-21 23:50

Sorry, it is impossible to tell what may be the problem without access to your system.

Richard MacCutchan20-Dec-21 23:55

20-Dec-21 23:55

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.

Le@rner21-Dec-21 1:11

Le@rner

21-Dec-21 1:11

its my card storage connected on usb 3.0 port

on usb 2.0 its working fine

Richard MacCutchan21-Dec-21 2:30

21-Dec-21 2:30

You need to check in Settings to make sure it is accessible. You can try a simple copy from File Explorer as a start.

VS2019 - is there a way to dump, display or list what a projects macro definitions are?

jschell23-Dec-21 5:40

jschell

23-Dec-21 5:40

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.

charlieg20-Dec-21 4:43

Re: VS2019 - is there a way to dump, display or list what a projects macro definitions are?

20-Dec-21 4:43

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.

charlieg20-Dec-21 4:54