|
|
Use it any place that your would normally use the c style cast operator.
LPARAM lParam
LPCSTR szString = (LPCSTR)lParam;
LPCSTR szString = reinterpret_cast<lpcstr>(lParam);
However, if you can it is alot safer to use static_cast, because the compiler will check to make sure that there are define rules to cast from one type to another.
When you use reinterpret_cast, you are basically saying to the compiler:
SHUT UP, I know what I am doing, it is ok to treat object of type A as a type B object.
|
|
|
|
|
|
syntax for reinterpret_cast:
reinterpret_cast < type-id > ( expression )
example:
CFoo oFoo;
CFoo* poFoo = &oFoo;
CBar* poBar = reinterpret_cast<cbar*>(poFoo);
Caution should be used, because you are bypassing all of the compiler's safeguards against type conflicts, etc.
Sef Tarbell
"A mind all logic is like a knife all blade, it makes the hand bleed that wields it." --Rabindranath Tagore
|
|
|
|
|
syntax for reinterpret_cast:
reinterpret_cast < type-id > ( expression )
example:
CFoo oFoo;
CFoo* poFoo = &oFoo;
CBar* poBar = reinterpret_cast<CBar*>(poFoo);
Caution should be used, because you are bypassing all of the compiler's safeguards against type conflicts, etc.
Sef Tarbell
"A mind all logic is like a knife all blade, it makes the hand bleed that wields it." --Rabindranath Tagore
|
|
|
|
|
I am a fairly new programmer, i have been looking at MFC, and being the young person that I am would like to have a try at the art of game programming. From what i gather games can be made in both OpenGL and DirectX, but i do not know which is the best to use, and where i can learn about the programming techniques.
Could someone tell please inform me.
==================================================
When Your Mind Wonders...Where Does It Go???
|
|
|
|
|
As of DX8 I believe DX is easier and more powerful, a new OpenGL standard is on the way. OpenGl is cross platform though, if that is of any use to you.
I'd start with DX and then learn GL later if you want to, although the nehe site has excellent OpenGL tutorials that are free, so you may chose GL as a matter of economics.
Christian
The tragedy of cyberspace - that so much can travel so far, and yet mean so little.
|
|
|
|
|
OpenGL is available for many platforms where DirectX is Windows only.
Jeremy L. Falcon
"The One Who Said, 'The One Who Said...'"
|
|
|
|
|
Is there anyway to do this ?
Ex.:
I´ve a function
HRESULT blah(BSTR sString, BSTR* sResult)
sString is [in] and sResult is [out, retval]
I need to allocate a new BSTR in the second parameter... maybe subclassing the pointer that sResult has and letting the CComBSTR do the dirty work ? Any guesses ?
Mauricio Ritter - Brazil
Sonorking now: 100.13560 Trank
|
|
|
|
|
|
Hi !
Here is my problem :
I've created and connected a CClntSocket* object (derived from CSocket) in my app.
And I want to use this socket to send & receive data in a modeless dialog box.
How can I "pass" this socket to my modeless dialog box ?
Thanks in advance for any kind of advice !!
Laurent
|
|
|
|
|
Augment the dialog constructor with an additional CCIntSocket * parameter. Depending on what part (the dialog or the code using it) takes responsibility for the cleanup of this CCIntSocket *, you'll delete it in one place or the other.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Thanks ! but it is already done 
In fact, when I "start" the modeless dialog by :
AfxBeginThread( RUNTIME_CLASS(CMyDlgThread) )
there's no way I can pass parameters...
Am I missing something ?
|
|
|
|
|
Ummm... So, you're launching a separate thread to maintain that modeless dialog of yours, right? If so, then you can use the CREATE_SUSPEND flag when creating the thread, pass the socket pointer to some member variable in CMyDlgThread designed to that purpose and then call CWinThread::ResumeThread to start the actual execution of the dialog.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
The trick works ! Thank you !
Unfortunately I get an assertion failure on "sockcore.cpp", maybe a socket cannot be reused in another thread ?
Any idea ?
|
|
|
|
|
If you could post the actual assertion and the context where is signaled, maybe we'd be avle to figure out ehat's going wrong.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
You'll note that I achieved this successfully the other day. I came across all sorts of problems:
It seems that when you create a socket, various message maps and macros and stuff are set up internally. When these fire off, all sorts of odd stuff happens.
What you need to do it this:
1. Detach() your socket to get a SOCKET handle
2. Start your (User Interface type) thread, with THREAD_SUSPENDED
3. Tell you UI Thread object what the SOCKET handle is. ie, use a public member variable.
4. Resume your thread.
5. In your threads init function, create a new CYourSocket object, and Attach() it to the socket handle.
that worked for me.
jon
Sorry to dissapoint you all with my lack of a witty or poignant signature.
|
|
|
|
|
In fact I forgot to do the Detach/Attach procedure...
Now everything is working fine !
Thanks for your help !
|
|
|
|
|
Wow, second time you've answered that in as many days!
Sorry to dissapoint you all with my lack of a witty or poignant signature.
|
|
|
|
|
Yeah, I'm the CREATE_SUSPEND man 
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
I'm writing a complex C program with VC++ 6.0. This program is very low-level (OS-like), and will actually run on a non-PC device. So the program itself must be in portable C and cannot use any Windows-specific features or APIs. I’m doing primary development and simulation with VC++/Windows because it is a much more convenient IDE than what is available for the native machine.
Examining the program's state with the standard VC++ debugging features (local/global variables, memory window) is proving to be very tedious. I need some aids to help me display (and hopefully modify) the program-specific state in a more human-readable format.
I've been trying to learn about all the VC++ features that I never knew existed. It seems that some combination of Visual Basic Macros, Debugger Add-ins, and/or Visual Studio Automation Interface might be able to help me. But I need some advice from those who know more about these facilities.
The kinds of things I need to display are the program’s private internal:
- Heaps
- Stacks
- Data structures
- Object references
- Object contents
- Memory maps
- Configuration data
- Trace buffers
Initially, I would be happy with some simple display-only capability, such as just writing text to the console or debug output window. While I could do this with internal printf and trace statements, I’d prefer to do it “on demand”, for example, by invoking a VC++ Debugger VB macro.
Ideally, what I want is to be able to add some menu items and/or icons to the Debugger Toolbar. Selecting these items will launch custom code (written by me) which will display in a nicely formatted way my program's custom internal state. The next step beyond that is to display groups of items in their own custom Debugger GUI windows, and allow me to modify program data in those windows.
I realize that this is a lot of work, and amounts to writing pieces of my own custom symbolic debugger. But it might be worth it to me in the long run, especially when I realize that Visual Studio seems to be designed to support this kind of thing.
So ... I’d appreciate it if someone can point me to:
- Architectural documents
- "How to" documents
- API reference documents
- Sample code
that will help me in my quest.
Thanks a bunch!
Mitch Butler
|
|
|
|
|
|
Hello,
i have a problem that bugs me for weeks now. And the question is very simple: how can i obtain the tooltip text from any tooltip? (for example - tooltip text from the items in the taskbar (system tray) - like from icq )...
I'm really stuck here 
Please, does anyone have any kind of advice, code snippet, kind word ... 
Thank you in advance.
Best regards,
dejan
|
|
|
|
|
You'll need to check for the window's class (use GetClassName) to see if the window in question is a tooltip. A tooltip has a class of TOOLTIPS_CLASS.
As far as retreiving the text of the tooltip, look into TTM_GETTEXT message and use the SendMessage API with it. You "might" be able to use GetWindowText also, but that's just a guess because I've never tried it.
If you want a code sample, let me know.
Jeremy L. Falcon
"The One Who Said, 'The One Who Said...'"
|
|
|
|
|
Mr. Falcon thank you very much for your quick answer,
This is the part of code i use:
::GetClassName(hwnd, ClassName, 200);
if(strcmp(ClassName,"tooltips_class32") == 0) {
vidljiv = IsWindowVisible(hwnd);
if (vidljiv){
// nasoTool = SendMessage(hwnd, TTM_GETCURRENTTOOL, 0,(LPARAM) (LPTOOLINFO)&ti);
// if (nasoTool)
// ::MessageBox(NULL, ti.lpszText,"TOOLTIP INFO", MB_OK);
::GetWindowText(hwnd,WindowCaption,100);
::MessageBox(NULL, WindowCaption,"TOOLTIP INFO", MB_OK);
}
}
commented parts are the second solution (instead of the last two lines - getWindowtText and MessageBox)
Unfortunately neither solution works. GetWindowText returns an empty string and SendMessage returns 0. A guy from microsoft replied that, i quote "However, pointers cross process using SendMessage won't work."...
So it seems that catching tooltip text is not possible?!?
If you have any idea what else could i try please be so kind and post a reply.
I would like to thank you again for your efforts.
Best regards,
Dejan
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
