C / C++ / MFC

Re: Windows Authentication

1-Aug-06 7:23

What about LogonUser()? As long as you aren't too particular, it'll probably get you by. If not, see here.

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

"Judge not by the eye but by the heart." - Native American Proverb

Ravi Bhavnani1-Aug-06 7:27

Ravi Bhavnani

1-Aug-06 7:27

Perhaps you could use LogonUser()[^] (followed by a CloseHandle(), if successful)?

Caveat: This is just an educated guess. There may be a safer and more appropriate way to authenticate a user.

/ravi

My new year's resolution: 2048 x 1536
Home | Music | Articles | Freeware | Trips
ravib(at)ravib(dot)com

Re: Windows Authentication

Programm3r1-Aug-06 7:33

Programm3r

1-Aug-06 7:33

Thanx guys, I'll try that...

Regards

Programm3r

Dialogs - Background Color and Size/Positions

Reagan Conservative1-Aug-06 6:35

Reagan Conservative

1-Aug-06 6:35

I have a login dialog box that will need to be placed over two connected monitors.
1)I see in the MFC Library Reference that I can call CWinApp::SetDialogBkColor to set the background color for this dialog, but exactly how is this called? What if I don't have an InitInstance() member function --- do I need to define one?

2)Also, the login dialog must be modal so that access cannot be gained until an ID and PIN are valid. Is there a way to call two objects of the login dialog and have each one placed over each monitor?

3) Can a dialog box be positioned using CWnd::SetWindowPos(.....). If so, how is this accomplished with two monitors?

Thanks for the assistance.

John P.

Sarath C1-Aug-06 6:54

Sarath C

1-Aug-06 6:54

Hi John,

jparken wrote:
I can call CWinApp::SetDialogBkColor to set the background color for this dialog

As per the MSDN documentation, this function is obsolete. To set the background color of the dialog box, you must handle WM_CTLCOLOR. This message changes the color of the specified dialog box only.

jparken wrote:
What if I don't have an InitInstance() member function --- do I need to define one?

This function creating the primary thread (WinMain) for the application. without this function, your application will not be spawned.

jparken wrote:
Also, the login dialog must be modal so that access cannot be gained until an ID and PIN are valid. Is there a way to call two objects of the login dialog and have each one placed over each monitor?

i dont know more about this. please refer MSDN for more information. I think it is not a beset practice to show login on two screens.

SaRath.

"Where I am from, there is no plan B. So, take advantage of today becuase tomorrow is not promised. - 50 Cent"

My Blog | Understanding State Pattern

Reagan Conservative1-Aug-06 7:02

Reagan Conservative

1-Aug-06 7:02

Thnaks for the info --- my refernce books are a few years old. This is Microsoft's way of keeping the revenue stream coming in, I guess Smile | :)

)

John P.

Sarath C1-Aug-06 17:33

Sarath C

1-Aug-06 17:33

It's not happening in C++/Microsoft technologies, but also happens with popular languages like and Java and all.

SaRath.

"Where I am from, there is no plan B. So, take advantage of today becuase tomorrow is not promised. - 50 Cent"

My Blog | Understanding State Pattern

Hamid_RT2-Aug-06 9:41

Hamid_RT

2-Aug-06 9:41

(1) You can use WM_CTLCOLOR or WM_PAINT
(2) Hope I understood your question See CWnd::DoModal()
(3)for set position from a window see SetWindowPos(..) or MoveWindow(...)
I hope its helful for you

WhiteSky

CString to LPVOID

EpicYeti1-Aug-06 5:28

1-Aug-06 5:28

I need to send a CString into a parameter that is of LPVOID type. I've tried:

CString stuff = _T("...");
LPVOID info = stuff.GetBuffer();

foo ( info );

stuff.ReleaseBuffer();

but the data is lost. How should I go about doing this?

David Crow1-Aug-06 5:38

1-Aug-06 5:38

Try:

foo((LPVOID) ((LPCTSTR) stuff));

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

"Judge not by the eye but by the heart." - Native American Proverb

EpicYeti1-Aug-06 5:52

1-Aug-06 5:52

I tried that too, same thing. What I am trying to do is send form data to the wininet SendRequest(LPCTSTR, DWORD, LPVOID, DWORD) function. the LPVOID parameter is the POST data that you send with a HTTP Post header.

David Crow1-Aug-06 5:59

1-Aug-06 5:59

epicyeti wrote:
...same thing.

How are you confirming this?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

"Judge not by the eye but by the heart." - Native American Proverb

EpicYeti1-Aug-06 7:03

1-Aug-06 7:03

what does work is something like this:

CString header = _T("Content-Type: application/x-www-form-urlencoded");
CString m_data = _T("target=wininet");

char data[] = "target=wininet";
LPVOID postdata=data;
		
pFile->SendRequest(header, header.GetLength(), stuff, mdata.GetLength)

basically i'm sending to the URL www.codeproject.com the data to the search form on the main page. The code above will return an html file with the search results.

The calls to SendRequest() with the double cast and the call to GetBuffer() both return html files that have no search results. I'm inferring from this that no post data got sent.

David Crow1-Aug-06 7:22

1-Aug-06 7:22

epicyeti wrote:
what does work is something like this:

So what's the problem then (if you have a working solution)?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

"Judge not by the eye but by the heart." - Native American Proverb

EpicYeti1-Aug-06 7:35

1-Aug-06 7:35

The problem is that I can't set the char data[] in the last example. I have a CString variable that has the POST data in it, however I can't get the data in CString because it returns a const char*, and I can't set that to the char data[]. I also have no idea what the post data will be, and thus can't hard code it as I did in the working example.

That was me hard coding my test. In the release it can't be hard coded.

Is there a way I could effectively do this:

CString m_data = _T("...");
char data[];
data = m_data.GetBuffer();

David Crow1-Aug-06 7:43

Re: CString to LPVOID [modified]

1-Aug-06 7:43

epicyeti wrote:
Is there a way I could effectively do this:

CString m_data = _T("...");
char data[];
data = m_data.GetBuffer();

If data actually had a size associated with it:

char data[100];
strcpy(data, m_data);

Or:

const char *data = m_data; // assuming you do not need to modify the data

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

"Judge not by the eye but by the heart." - Native American Proverb

EpicYeti1-Aug-06 9:35

1-Aug-06 9:35

I finally got it to work.

So the CString::GetBuffer() returns a const wchar_t* not a const char*, I was mistaken. Howerver I could still use the method you suggested:

const wchar_t* data= m_data.GetBuffer();

If I send that into the SendRequest function the wide char data is lost or not converted or something. So I had to convert it to a char*:

const wchar_t* data= m_data.GetBuffer();
m_data.ReleaseBuffer();

char* Cdata;
Cdata = new char[m_data.GetLength()+1];
size_t num=m_data.GetLength();

wcstombs_s(&num, Cdata, num+1, data, num);
LPVOID postdata=Cdata;

This seems sloppy to me, but it gives the correct output when I use postdata in the SendRequest function. Thanks for all your help!

-- modified at 15:42 Tuesday 1st August, 2006

Zac Howland1-Aug-06 8:43

1-Aug-06 8:43

epicyeti wrote:
Is there a way I could effectively do this:

CString m_data = _T("...");
char data[];
data = m_data.GetBuffer();

Did you read the response from 2 hours ago?

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac

EpicYeti1-Aug-06 9:38

1-Aug-06 9:38

Yeah, I'm sorry I didn't respond.

the strcpy doesn't take a CString varriable. I could have used GetBuffer on it, but I would probably would have had to conver the returned wchar_t to a char like I ended up doing. My real issue evidently was with sending the SendRequest function a wchar_t* instead of a char*.

Thanks for your input, and again I am sorry I didn't respond.

Zac Howland1-Aug-06 10:02

1-Aug-06 10:02

epicyeti wrote:
the strcpy doesn't take a CString varriable

It does because CString has an explicit LPCTSTR operator to do the casting. The problem is actually that you have UNICODE enabled (apparently), in which case you need to convert it from wchar_t to char* first. Alternatively, you could pass the data in UNICODE format, but you would need to pass the size as double the length of the string and specify that you are using UTF-16 as your text format in your HTTP headers.

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac

EpicYeti1-Aug-06 10:57

1-Aug-06 10:57

Your signature is true to life. I'll be sure to know if I am using UNICODE from now on, and I'll be more careful with my headers. Thanks again for your input.

Zac Howland1-Aug-06 6:05

1-Aug-06 6:05

epicyeti wrote:
SendRequest(LPCTSTR, DWORD, LPVOID, DWORD) function. the LPVOID parameter is the POST data that you send with a HTTP Post header.

You will probably need to do this:

CString strPostData = _T("Some POST Data");<br />
char buffer[100] = {0};<br />
strcpy(buffer, strPostData);<br />
pHttpFile->SendRequest("POST", dwSomeDword, (LPVOID)buffer, strlen(buffer) + 1);

LPVOID is defined as void*. Using the LPCTSTR operator for CString will return you a const char* (when UNICODE is not defined). The const keyword is the main thing you should be worried about there. The fact that SendRequest does not ask for a const void* indicates that it may try to write to that buffer, which would cause problems if you tried to pass in the CString object itself.

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac

Zac Howland1-Aug-06 5:51