C / C++ / MFC

Storage class for MD5 values

12-May-07 5:43

Something like this...

PROCESS_INFORMATION ProcessInformation;
 
if (::CreateProcess(..., &ProcessInformation))
{
   // <code>Note you may want to use a timeout value instead of INFINITE</code> :)
   ::WaitForSingleObject(ProcessInformation.hProcess, INFINITE);
 
   ::CloseHandle(ProcessInformation.hProcess);
   ::CloseHandle(ProcessInformation.hThread);
}

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

TariqZ11-May-07 18:39

TariqZ

11-May-07 18:39

I want to store a bunch of MD5 strings computed from username/password. Have any storage class to facilitate this?
Thanks

Re: Storage class for MD5 values

Garth J Lancaster11-May-07 19:27

Garth J Lancaster

11-May-07 19:27

whats wrong with std::vector<std::string> ?

it really depends on what you wish to do with the results

'g'

Second Slider won't slide with setcapture

mtwombley11-May-07 13:05

11-May-07 13:05

I have a CDialog derived class (CColorSliderDlg) that has three scroll bars on it.
CColorSliderDlg doesn't have a border and so uses the SetCapture to detect when the mouse has been clicked outside it.

Because I'm using SetCapture the child controls will not get any mouse messages. So in the PreTranslateMessage I check if the message should go to a child and forward it to it.

BOOL CColorSliderDlg::PreTranslateMessage(MSG* pMsg)
{
	//Because we have a capture set, mouse messages don't forward to the children.
	//So help out and forward them, just do it for mouse messages as the rest seem to work
	POINT pnt = pMsg->pt;
	ScreenToClient(&pnt);
	CWnd *child = ChildWindowFromPoint(pnt,CWP_SKIPINVISIBLE);
	if (child != 0  /*&& child != this*/)
	{
		pMsg->hwnd = child->GetSafeHwnd();
 	}
		
	return CDialog::PreTranslateMessage(pMsg);
}

When the mouse is released for the slider I set the capture back.

void CColorSliderDlg::OnHScroll(UINT nSBCode, UINT nPos, CScrollBar* pScrollBar)
{	
	if (nSBCode == SB_ENDSCROLL)
		SetCapture();
	CDialog::OnHScroll(nSBCode, nPos, pScrollBar);
}

This works great on the first slider on the dialog.
When I added the other two only the first one will respond.
If I tab and use the keys or the wheel mouse the slider will move. But click and drag just won't.

If I remove the SetCapture everything works great again but I can't close the dialog.

Thanks
Mark

Mark Salsbery11-May-07 13:25

11-May-07 13:25

mtwombley wrote:
This works great on the first slider on the dialog.
When I added the other two only the first one will respond.

According to the docs:

"Only one window at a time can capture the mouse."

mtwombley wrote:
CColorSliderDlg doesn't have a border and so uses the SetCapture to detect when the mouse has been clicked outside it.

I'm not sure what you're trying to do. If the mouse moves outside the slider then you'll get
WM_LBUTTONDOWN, WM_MOUSEMOVE, etc. messages at the underlying dialog.

Maybe another solution would be to use TrackMouseEvent() on the sliders to tell the system they
should receive WM_MOUSEHOVER and WM_MOUSELEAVE notifications. Then you don't have to fight the
mouse capture stuff.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

mtwombley11-May-07 13:57

11-May-07 13:57

Thanks Mark for the reply.
I'm not doing the SetCapture on the slider. I'm doing it on the dialog so it knows when the user clicks outside of it and can then close.

My dialog is based on a Color Picker by Luis Ortega http://www.codeguru.com/cpp/controls/buttonctrl/article.php/c2089/.
Luis showed a grid of buttons for the colors and then had an other button.

For my application I wanted to have three sliders for color selection.
I placed one slider on the dialog and got that working which was great. But as soon as I added the other two they stated to act funny. If SetCapture is on the dialog the first slider is the only one that responds.

Hope this clears up my question.

Thanks

Mark Salsbery11-May-07 14:39

11-May-07 14:39

Thanks for more info!

mtwombley wrote:
I'm doing it on the dialog so it knows when the user clicks outside of it and can then close.

Maybe this works but here's another line from the docs:

"SetCapture captures mouse input either when the mouse is over the capturing window, or when the
mouse button was pressed while the mouse was over the capturing window and the button is still
down."

I would think when you drag a slider, the slider control is going to capture the mouse so the
dialog will lose the capture anyway.

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

mtwombley11-May-07 15:24

11-May-07 15:24

Actually that does happen.

But only on the first slider on the dialog. For some reason the other sliders will not accept the first message. I say the first because if you click it twice then it starts working.

Mark

Mark Salsbery11-May-07 16:01

11-May-07 16:01

I tested your code.

I can't move any trackbars until I click on the cancel button but drag the cursor off it before
releasing - that releases capture from the dialog. Then I can drag a trackbar thumb.

I think the PreTranslateMessage() needs to really only pass certain mouse messages to the child
under the cursor, not all messages. I would guess that WM_SETFOCUS and WM_PAINT, at the very
least, are going to be a problem in the current implementation.

I'm still playing with it but I'm about to be interrupted for dinner.

I shall return.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

mtwombley12-May-07 10:18

12-May-07 10:18

Thanks Mark for looking into this. I was just trying to build on some existing code not realizing I would have so much trouble.

I've got a deadline I need to meet so I'm just going to put a tool window on the dialog and the user can close it when they are done.

Later I might come back to this or just create a CWnd that contains the sliders and don't use the DoModel().

So many ways too do something.

Thanks again

Mark

Mark Salsbery12-May-07 14:05

How to obtain a DLL window handle

12-May-07 14:05

Oh it's modal too? I was testing modeless Smile | :)

There should be an easier alternative with a modeless dialog. You can use focus or activate
messages to close the dialog when the user leaves it.

Good luck!
Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

LogonUser to windows xp

jluis_hdezg11-May-07 10:15

jluis_hdezg

11-May-07 10:15

I have a dll that runs two functions:
One is to disable the USB porst....
TWO is to change the WinLogon keys: DefaultUserName and DefaultPassword.

These two functions use the LogonUser function that I pass the administrators account. It does not works fine the first time executing like this.

USB
WINLOG AS LIMMITED ACCOUNT

Everytime I try to LogonUser the user after executing the second function it gives me an error: Uknown user name or bad password.

Everytime I do it I use administrator's account.

Any help will be greatly appreciated.

Regards,

Jose

Perspx11-May-07 10:05

Perspx

11-May-07 10:05

I have written some code which injects a DLL into another process, in order to add a new menu item into the process's window menu. However, once I inject the DLL into the process, I'm not sure how to find out the window handle of the process which I've injected the DLL into - and this code needs to be executed within the DLL, as I am using SetWindowLongPtr() with GWLP_WNDPROC so that I can monitor the window messages to find out when the menu item has been selected. Also note that this DLL is intended to be injected into all the visible running processes and add the menu item to each process's main window.

Thank you for your help

-- PerspX

Re: How to obtain a DLL window handle

Randor 11-May-07 10:54

Randor

11-May-07 10:54

Try something like this...

<br />
VOID SomeClass::EnumerateWindows()<br />
{<br />
	EnumWindows(EnumWindowsProc,0);<br />
}<br />
<br />
BOOL CALLBACK EnumWindowsProc(HWND hWnd, LPARAM lParam)<br />
{<br />
	DWORD dwPID = 0;<br />
	GetWindowThreadProcessId(hWnd,&dwPID);<br />
}<br />

A window is the 'main' window of a process if it has no Hwnd parent within same PID. But keep in mind... some processes can have multiple 'main' windows (such as Outlook). A more correct term to describe these windows are 'Top level windows'

Good Luck,
-Randor (David Delaune)

Re: How to obtain a DLL window handle

Perspx13-May-07 8:42

Perspx

13-May-07 8:42

Thanks

- it works really well and to find out which process owns the DLL, I just compare the result from GetWindowThreadProcessId() with the PID from GetCurrentProcessId()

--Perspex

Error debugging winsock programs?

raul211-May-07 9:08

raul2

11-May-07 9:08

Hello
When i use VS6 to write winsock apps, they run normally, but when i try to debug them, i reach the line that initializes the socket :
sock = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
or whatever
and when i press F10 to step over it, i get a runtime error:
First-chance exception in UdpTest.exe (NTDLL.DLL): 0xC0000008: Invalid Handle.
i tried lots of source codes from lots of sites
i have WinXP Pro SP2
Can anybody help me plz
Thanks in advance

Mark Salsbery11-May-07 9:29

11-May-07 9:29

Have you called WSAStartup() before using any Winsock APIs?

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

raul211-May-07 10:19

raul2

11-May-07 10:19

yes i did
here's the line
if (WSAStartup(MAKEWORD(2,2), &data) != 0) return(0);

Mark Salsbery11-May-07 10:22

11-May-07 10:22

After re-reading your post...does an unhandled exception actually occur or do you just see
the first-chance message in the debug output?

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

raul211-May-07 12:19

raul2

11-May-07 12:19

not in the output .
A pop-up message comes out saying first chance exception ...
then it takes me to assembly window.

Mark Salsbery11-May-07 12:26