|
Thank you for your help,
but, does it make any difference when it is developed for PocketPC devices?
Thanks in advance
Mohammad
And ever has it been that love knows not its own depth until the hour of separation
|
|
|
|
|
Only if DX or OGL are not available on the PPC
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
I posted a Q about memory leak and got suggestion to use the tool:
Visual Leak Detector
I linked all as instruction and run in debug, but I see Nothing related to the tool, it looks that the tool doesn't exist:
No interface, no text, no god, no ghost, no ...
every thing is exactly the same as before.
what is that? have u used the tool in someway?
I think I should see something about the tool.
any comments?
-- modified at 15:56 Thursday 10th August, 2006
|
|
|
|
|
why don't you ask your question in the comments of the article of Visual Leak Detector ?
|
|
|
|
|
includeh10 wrote: I think I should see something about the tool.
What?
includeh10 wrote: any comments?
Yes. Why did you start another thread for the same question?
led mike
|
|
|
|
|
When the process exits, it'll dump the memory leak information to the debug stream. Since the output is formatted in such a way that Visual Studio understands, you can double click on the output, and the IDE will open the right file and put the cursor on the line on which the leak was detected.
The 1.0 version works very well. The coming 2.0 (dunno when it'll come, last time I talked to the author, he was bogged down with work), will detect lots more than just memory leaks. Interesting stuff.
Anyway, I use the 1.0 successfully at home, and is thinking about using it at work. If you're looking for a nonexpensive tool to find memory leaks, I really recommend VLD.
--
Hey, TiVo! Suggest this!
|
|
|
|
|
Oh by the way, you will need to recompile the library for later versions of Visual Studio than VC6. Otherwise it'll report nothing. Since it was written in VC6, it contains a great deal of code which is not standards compliant. If you'll mail me, I will reply with source code that compiles and works well with Visual Studio 2003.
--
No humans were probed in the making of this episode
|
|
|
|
|
I posted a Q about memory leak and got suggestion to use the tool
Visual Leak Detector
I linked all as instruction and build in debug version - but I see Nothing related to the tool:
no interface, no text, no ...
Any thing is the same as the tool does not exist.
what is that?
have u used the tool someway?
|
|
|
|
|
you didn't mention "running the app under the debugger".
led mike
|
|
|
|
|
Hi,
I've set up GDI+ in an application but i onldy get unresolved linker errors.
The compiler can't find "_GdiplusStartup@12" and "_GdiplusShutdown@4".
Does anyone knows what i can do to get GDI+ running?
thx
|
|
|
|
|
nightrider13 wrote: 've set up GDI+ in an application
What do you mean the you setup GDI+ in an application? Did you include gdiplus.h? Link to the gdiplus library? Tell us what you did do and maybe someone can tell you what you didn't do...
|
|
|
|
|
Yeah you're right, sorry
Yes I already included gdiplus.h. Then the next step was to declare these variables in CWinApp derived class:
private:
GdiplusStartupInput m_gdiplusStartupInput;
ULONG_PTR m_pGdiToken;
After that I added at the beginning of the InitInstance:
GdiplusStartup(&m_pGdiToken,&m_gdiplusStartupInput,NULL); //gdi+ init
And in the ExitInstance:
GdiplusShutdown(m_pGdiToken);
Thats it!
Next step was compiling.
|
|
|
|
|
nightrider13 wrote: Yeah you're right, sorry
No problem. Was half afraid that I came on too strong. I get alot of "it's broke" type stuff...
I could be wrong but I think that you need to add the gdiplus.lib to your project linker properties.
|
|
|
|
|
Yeah you aren't wrong, that was the problem.
Thank you Wes!
|
|
|
|
|
No problem. Glad that was it.
|
|
|
|
|
In my wndProc(Message* m) function
PDEV_BROADCAST_HDR lpdb;
case DBT_DEVICEARRIVAL:
// Handle device arrival
// treat lParam a pointer to a standard structure DEV_BROADCAST_HDR
lpdb = (PDEV_BROADCAST_HDR)(m->LParam);
// check if an volume device arrival
if (lpdb->dbch_devicetype == DBT_DEVTYP_VOLUME)
I received error:
error C2440: 'type cast' : cannot convert from 'System::IntPtr' to 'PDEV_BROADCAST_HDR'
No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
How to resolve it????
|
|
|
|
|
Hi
Is it possible to do message maps calls like post and peakmessage from a non-GUI (no window) application? I have an MFC dll with callbacks that i presume can be invoked using message map calls. But as i understand these calls requires a window handle and as there is no window/UI (its a service) I am not sure how i can invoke these callback from the dll.
Are there any related sample code or articles that i can look at?
TIA
-S
PS: I am not very experienced with mfc programming so please bare with my silly questions.
|
|
|
|
|
shreelak wrote: I have an MFC dll with callbacks that i presume can be invoked using message map calls. But as i understand these calls requires a window handle...
What would those callback functions do with a NULL window handle?
"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
|
|
|
|
|
I didn't try that. I shall try it now post my results
thankyou
|
|
|
|
|
This is possible.
Hope ur ServiceMain is in a separate thread. u can use PostThreadMessage to post any message. Then in a loop you can chk for the messages by calling GetMessage or PeekMessage.
cheers.. Milton KB
|
|
|
|
|
Is there an activeX or DLL that I can use that emulates the Insert
Hyperlink GUI of MS Access? I'd hate to have to code all the beauty
that's already there.
Thanks,
Tony
|
|
|
|
|
When I send a CString to my multiline read only edit control it displays boxes for all of the newline characters. Is there a way to make it automatically move the text to the next line when it encounters a '\n' instead of displaying the newline character?
Thanks
|
|
|
|
|
|
|
See Here[^] maybe it is some helpful to you
|
|
|
|