|
If I press F10 0r F11, it just goes to the next line not to the draw() function definition.
|
|
|
|
|
Are you debugging the Release mode?
Otherwise make sure to disable optimization in Project -> Properties -> Configuration Properties -> C/C++ -> Optimization -> Optimization .
|
|
|
|
|
Did u mean Full optimization i.e /Od? There's no Optimization in this Project -> Properties -> Configuration Properties -> C/C++ -> Optimization ->
If I set this, I got the following error:
Command line error D8016 : '/Ox' and '/RTC1' command-line options are incompatible
|
|
|
|
|
I meant optimization should be /Od.
If optimization is disabled and you're in debug mode, you should be able to step into the draw function by pressing F11 unless the draw function is in another DLL or library.
|
|
|
|
|
I'm in debug only. I misunderstood ur prev. post. It's Irrlicht Engine's function. I can't step into this by pressing F11. If I press F11, control moves to the next line. It's a virtual function and is defined in a file called IGUIElement.h like this:
virtual void draw()
{
if ( isVisible() )
{
core::list<IGUIElement*>::Iterator it = Children.begin();
for (; it != Children.end(); ++it)
(*it)->draw();
}
}
|
|
|
|
|
Is this the final version?
I mean have you overloaded it?
You could put a breakpoint inside this function and try to debug.
|
|
|
|
|
Not overloaded. I'm calling it with a derived class's object. All the Buttons and other elements are derived from IGUIElement.
|
|
|
|
|
T.RATHA KRISHNAN wrote: When running my application, it suddenly crashes and goes to this line:
You always forget to supply important information while asking a question. A really important information in this case is the exact error message. What does it say exactly ?
|
|
|
|
|
Is it possible you've deleted your pointer elsewhere? If so, NULL your pointer every time you delete it, so you can find this bug more easily.
Or the function that created the pointer did it badly, and returned a pointer to a stack variable. If so, it might work for a while, until the memory got re-used...
The 0x4ea5608 looks like a legitimate pointer value - so it was probably correct, even if only briefly.
Iain.
I am one of "those foreigners coming over here and stealing our jobs". Yay me!
|
|
|
|
|
Hi,
The data located at your m_pBackButton pointer address is the magic number 0xFEEEFEEE which is used by the MSVC debug heap and this would imply that your m_pBackButton has been deleted.
Best Wishes,
-David Delaune
|
|
|
|
|
Hello,
I am getting this error :
0x80040111 ClassFactory cannot supply requested class
I already done regsvr32 for the C++ ATL dll file.
When I check the registry, I can find the entry at HKEY_CLASSES_ROOT\CLSID.
InProcServer32 has the dll path as the default while threading model is Apartment.
I verified that there are entries in regedit for :
- clsid
- typelib
- event
- interface.
I called the CoInitialize as below :
HRESULT hr_init = ::CoInitialize(NULL);
if (FAILED(hr_init))
{
return E_FAIL;
}
HRESULT hr_init2 = m_spIEventFiringObject.CreateInstance(__uuidof(EventFiringObject_OD));
if (FAILED(hr_init2))
{
return E_FAIL;
}
m_pIEventFiringObjectEventHandler = new IEventFiringObjectEventHandler(*this, m_spIEventFiringObject, &CManualTest::OnEventFiringObjectInvoke);
When I run debug, CWinApp::InitInstance() was successful.
It fails at _AtlModule.DllGetClassObject(rclsid, riid, ppv);
When I run the client software, it fails with ClassFactory cannot supply requested class error.
Your guidance on solving this problem is very much appreciated.
Thanks,
Goutam
|
|
|
|
|
How is m_spIEventFiringObject declared?
Did you do #import to instantiate the COM component?
|
|
|
|
|
Thank you for trying to help.
This is the declaration :
IEventFiringObject_ODPtr m_spIEventFiringObject;
This is from the tlh file (which shows declaration of IEventFiringObject_ODPtr) :
_COM_SMARTPTR_TYPEDEF(IEventFiringObject_OD, __uuidof(IEventFiringObject_OD));
The StdAfx.h contains :
#import "D:\Project\ODepth\ODepth\Debug\ODepth.dll"
using namespace ODepthLib;
I am using below project as sample/template file :
Understanding COM Event Handling[^]
I just made some changes to make sure my program does not clash with the sample file.
The sample file works fine, while my program errs.
|
|
|
|
|
Is there any other information I need to provide?
|
|
|
|
|
ggoutam7 wrote: Is there any other information I need to provide?
Hi,
The value of the HRESULT will tell you more information about why CreateInstance failed.
Best Wishes,
-David Delaune
|
|
|
|
|
HRESULT for CreateInstance has the value of :
0x80040111 ClassFactory cannot supply requested class
Can you please guide me on how to fix this 0x80040111 ClassFactory cannot supply requested class error?
|
|
|
|
|
hello guys....well im not master on reading the msdn documentation. Can you plz tell me how to find the right topic(i mean, where it is located)...am i the only one in this universe to ask this question??
|
|
|
|
|
MSDN is a bitch to use.
1. use google to search MSDN, prefix your searches with "site:msdn.microsoft.com".
for example, type this in google "site:msdn.microsoft.com CWnd" ...
2. if the links do not work inside the "offline" MSDN, goto 1.
Watched code never compiles.
|
|
|
|
|
I also prefer google search for MSDN. If searching at MSDN site directly, the results generally are not in the order of importance that I expect. It could be my misconception.
TOMZ_KV
|
|
|
|
|
I Also avoid Bing in MSDN, and Use Google... Sorry Bing.
Results are closer to what i'm looking for, however I user a search such as: MSDN C# System.Core...etc..
this will give a little more info (IMO) because it will give you context, and a dash of outside perspective (Lower on the gage).. and I usually iterate between MSDN and Web until I hone in on what Exactly I'm looking for on msdn.. I've found that the MSFT blogger5s usually have better info on their blogs then the Documentation and the links to the documentation are often in the blog.. a Great example of this is if you try to figure out how/when to use a spin lock....I spend 4 hours on Sunday until I found a random comment on some MSFT blog that actually explained the intricacies of it.
If your interested I think it is an great example of how the documentation is worthless...(actually says that you shouldn't use it really ever).. whereas one blog says it will cause a serious performance hit, and the final one an article about memory management says that it is faster before a threshold....
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
|
|
|
|
|
Good experience to share. I remember several years ago, Microsft had an invitational meeting for developers in New York to collect feedbcks to improve the search for MSDN documentation.
That was before BING time. Then the BING took over. As a result, whatever BING does is what we get. No particular search improvement on MSDN could be seen.
TOMZ_KV
|
|
|
|
|
Just Bing it!
|
|
|
|
|
Just go to the MSDN Home Page[^] and use the search facility. However, you will find that many search items will return multiple 'hits' so you sometimes need to review more than one link before finding the correct one. For example when searching for CheckMenuItem I got this page[^], but since I know I'm searching for a Windows function I can fairly easily trust that the first hit is the correct one. Try the same thing with a .NET function and its a little more difficult. The only way to get really comfortable with it is to use it as much as possible and you will soon grow to love(???) it.
Don't forget to customize it to your own requirements in terms of country and view type.
It's time for a new signature.
|
|
|
|
|
<and you="" will="" soon="" grow="" to="" love(???)="" it.="">
Good to see that the art of sarcasm is alive and well !
|
|
|
|
|
Just don't. No good can come of it. All you'll get from MSDN is an impeneterable generic entry, nonfunctional "example" code and a restatement of the parameters that you already got from intellisense.
Do yourself a favor, search with google and open the first NON-MSDN link returned. The only thing I ever got from MSDN was hypertesion and a nervous tick.
|
|
|
|