Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
Quote:
Originally Posted by
emarusso
Nothing changes, the error's still there.
You are specifying a constant, and now it doesn't work? Before you said it did work when you specify a constant.
Regards,
Paul McKenzie
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
Quote:
Originally Posted by
emarusso
No, the prototype is
void put_FileName(LPCTSTR newValue).
As written in QTControl.h, that I attached.
You didn't attach code. You had a link to a site that my browser policies refuses to go to.
Actually attach the code, don't link to another site.
Regards,
Paul McKenzie
1 Attachment(s)
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
The zip file contains the code from the link.
Attachment 31445
1 Attachment(s)
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
Quote:
Originally Posted by
2kaud
Where do you hard code the URL? I suggested a test of a hardcoded URL in my post #10 but you replied that this still causes the problem.
When I wrote hardcoded I meant that I wrote it in the visual studio resource editor, in the property window.
Attachment 31449
What you said was to hardcode the string in the function call.
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
thanks for re-attaching it, I didn't know how to attach it to the thread.
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
Quote:
Originally Posted by
emarusso
thanks for re-attaching it, I didn't know how to attach it to the thread.
Then read the Announcement: Before you post....
BTW, is your MFC project a UNICODE or ANSI one? And the same question - about QuickTime ActiveX Control.
Re: Help request: QuickTime ActiveX Control Heap Corruption the second time I open a
My sample is UNICODE, I tried to compile it multi-byte but the problem's still there.
I don't know wether the ActiveX is UNICODE, and I don't know how to check it.