When I debug this code the value for cstring is the URL I need! However, when I try to view it with AfxMessageBox or Navigate to it, it still thinks the value is all question marks.... I don't understand why it could show me one thing and do another... I wish there was a way to post a screenshot....
Unless it's on mulitple locations on my drive the version I have appears to be older... I have 6.0.2900.2919. According to the article on MSDN: NewWindow3 is available only in Microsoft Windows XP Service Pack 2 (SP2) or later. So if you have that, it should work...
FYI, after messing around a bit and not getting anywhere I put the code back that was showing me the proper URL in the debugger stopped working again. Same code, but bad results. I have't been able to get it to reproduce the proper URL in the debugger since.
This is the correct behavior. The cursor is a shared system resource, no one app is allowed total control over it. Imagine if ClipCursor() worked 100% of the time. All you'd have to do was write an app that calls ClipCursor(0,0,1,1) and boom - instant denial of service.
where else do you think you can dynamically allocate some memory ?
In multiple heap scenarios you can define your own memory segments to specify which area of memory is used to allocate various elements such as messages, semaphores etc. I have a feeling that this is processor dependend and not something that I can do with C standard functions. Is there a way of doing this without depending on the platform being used? I realize that my previous question is not clear enough and I apologize for that. I must stress that this is a Real-Time programming related question.
In my Form1 (VC++ .NET framework), I first need to add prototype of WindowProc in header file. Which section shall it be added private, protect, or public??
Is following prototype correct?? LRESULT CALLBACK WindowProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam);
Is following implementation function header correct?? LRESULT CALLBACK Form1::WindowProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)