|
Hi,
You can use Strcmp function to compare two strings.
Regards
Velayudhan
|
|
|
|
|
use CString::Find if your string isnt exist return value of Find is -1 else its location of string
|
|
|
|
|
I found that some *.cpl have exported many useful functions.
how colud I launch some export function?
for example:
in firewall.cpl,there are some export functions:
CPlApplet
Install
ShowControlPanel
ShowNotificationDialogW
Uninstall
Thank you 
|
|
|
|
|
Run control.exe to launch an applet, for example:
control %systemroot%\system32\firewall.cpl
|
|
|
|
|
Thank you. I knew how to launch an applet.
I mean how to launch an export function of an applet.
|
|
|
|
|
I have a strange problem within a CDialogBar. I need to paint some text in a different font, so I used a static box which I paint over. I capture the WM_PAINT message as OnPaint().
What I intended to do was invalidate the static box to cause a paint command, then inside the SetPatInfo() routine (inside the paint), validate the static box. There seems to be a timing problem as first my routine draws to the box and then another message comes along which updates the static box.
I can verify this by making the CDialogBar disappear from the screen and then reappear, in which case there is no invalid area and just my update is performed under the OnPaint().
I went farther to prove it by invalidating just 1/2 of the box in which case only 1/2 of the box is overwritten after I update it. My question is: why doesn't validateRect stop the second update and where is the second update coming from?
A solution to the problem is to update a single pixel in the corner of the box, but I want to know what is going on and why. Here are some code snippets:
void CMyToolbar::OnPaint()
{
CPaintDC dc(this); // device context for painting
SetPatInfo();
}
void CMyToolbar::Invalidate(void)
{
CWnd *wnd1;
CRect rc1;
wnd1 = GetDlgItem(IDC_PATINFO);
wnd1->GetClientRect(&rc1);
rc1.right /= 2; // for test, invalid 1/2 of rectangle
wnd1->InvalidateRect(rc1,0);
}
void CMyToolbar::SetPatInfo(void)
{
.....
wnd1 = GetDlgItem(IDC_PATINFO);
pDC = wnd1->GetDC();
.....
wnd1->GetClientRect(&rc1);
wnd1->ValidateRect(NULL); // NULL validates the whole window
sz1.cx = rc1.right;
sz1.cy = rc1.bottom;
br1.CreateSolidBrush(bkgColor);
pDC->FillRect(rc1, &br1);
.....
}
Any suggestions to telling me what is going on here would be appreciated.
Ilan
|
|
|
|
|
try Validating the rect after completing drawing operation i.e. call ValidateRect after calling FillRect.
|
|
|
|
|
Ovidiu answered my question in previous question which I unfortunately didn't see until after posting this message. His answer is:
As long as you have not handled WM_PAINT in the static control, but you draw text in it from another place, for sure you'll have troubles after another window will overlap; just test it and see if I'm right.
Ovidiu
He is ABSOLUTELY right and now I have to figure out how I can handle just the WM_PAINT for that static control. I see a WM_PAINT for the DialogBar but I can't find a separate one for just the static control.
BTW, in answer to my response, it makes no difference if I do the validateRect before or after the FillRect. I'm sure Ovidiu is on the right track, but I just have to figure out how to do it.
|
|
|
|
|
quite right.
I think you need to override CStatic class to use in you app.
|
|
|
|
|
I would like to know how to write a hidden program (it will not display in the task bar).
Please help!
|
|
|
|
|
Try using the WS_EX_TOOLWINDOW extended style when you create your window.
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
Is it possible to use MFC to do this?
|
|
|
|
|
Yes. But you'll need to use CWnd::CreateEx instead.
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
But what type of application I should chosen to create?
Could you give me more detail steps?
Please help!
|
|
|
|
|
I programm it with vc+++ and mfc,atl.
does this has anything to do with the difference of the operating system? if dose, how to fix it? if not, what could have been the cause?
Thank you very much!!!
-------------------
I am learning C++ and English
|
|
|
|
|
can you be more specific? Is that dll links with any dll supported on XP?
use depends.exe in visual studio to see dependency.
|
|
|
|
|
I detected four files my dll depends on with a software named Setup Factory. all of them are located in the system folder of window, which I think will be the reason and I have not had a chance to test it.
Thank you very much!!!
-------------------
I am learning C++ and English
|
|
|
|
|
Run depends.exe, on both OS, if its shows some missing dll. Try to ship it with your dll, and test.
|
|
|
|
|
Hello,
I have matther with how to detect the memory infromation in windows platform. I want to get the some memory information, just as memory total size, memory type, memory manufacture, memory frequency, and so on. just the memory information in windows platform. Can you help me? How to do that? I hope your reply, thanks.
Hanson David
|
|
|
|
|
|
|
Dear WhiteSky,
Thanks for your kindly help, I have review the WMI correlative knowledge, but I don't how to implement it. Can you give me some example using the WMI method to get system information, thanks.Hope to get your help...
|
|
|
|
|
well i see your reply now.did you see this link is your problem solve?
|
|
|
|
|
HansonDavid wrote: I want to get the some memory information, just as memory total size, memory type, memory manufacture, memory frequency, and so on. just the memory information in windows platform.
This will get some of what you're looking for:
<br />
void some_function(void)<br />
{<br />
LPMEMORYSTATUS buffer;<br />
<br />
::GlobalMemoryStatus(&buffer);<br />
}<br />
The MEMORYSTATUS buffer looks like this:
<br />
typedef struct _MEMORYSTATUS {<br />
DWORD dwLength;<br />
DWORD dwMemoryLoad;<br />
DWORD dwTotalPhys;<br />
DWORD dwAvailPhys;<br />
DWORD dwTotalPageFile;<br />
DWORD dwAvailPageFile;<br />
DWORD dwTotalVirtual;<br />
DWORD dwAvailVirtual;<br />
} MEMORYSTATUS, *LPMEMORYSTATUS;<br />
GlobalMemoryStatus() is inside winbase.h, and I think MFC includes this by default, so you probably don't need any extra headers.
-Greg Dolley
|
|
|
|
|
Greg Dolley,
Thanks for your help, but I expected to get more information, not only the memory size. Bascially, I want to know the all dimm socket memory information, including the memory size, memory type, memory manufacture, and so on. Mabye the Win32_PhysicalMemory class of WMI will helpful to me, but I don't how to use it, can you help me? thanks.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
