CFileDialogs are pretty much as simple as it gets... with that said, your question doesn't make a ton of sense. What's error that you're getting exactly? Is it a breakpoint or a assertion that's stopping execution?
Place applicable code and maybe I can get a better idea as to what you're doing wrong.
That exactly the point I had the contructer coded with filers window title etc.
but this code
This what happens when I step to mydialog.DoModal();
The code hits a break point
and later on get a access violation
doing a Call Stack at this point seems that mscowrks.dll is executing
I moved this code to the beginng of CWinApp::Initinstance
so Its one the first things I do and still I have problem
You're probably compiling this with some odd options, that's part of .Net (I believe), which you shouldn't be using at all on a C++/MFC application. I would guess your problem is not the code but the way you configured the project.
Assuming this is a continuation of your previous problem, I already suggested this[^], and similarly tried to explain, here[^], about the correct use of casts in C. Randomly changing parameters or removing them altogether is no substitute for making full use of both documentation and debug information.
Should work as it would take default paramters correct ?
Not necessarily, as we do not know what else your code is doing. As I said before, read the documentation[^] and carefully check against your code. Also ensure that your project has been completely rebuilt to ensure no undiagnosed compiler errors remain.
There's a known problem with CFileDialog crashing although I can't remember the exact situations. Something to do with WINVER, I think. Anyway, you can test if this is what your problem is by creating the dialog on the stack and seeing if that stops the crash.
CFileDialog* pFD = new CFileDialog(...);
OK I did embark into world of DirectShow and ditched VFW.
All the code samples here is way over my head for now.
I got as far as “using SDK to build basic DirectShow”. It is in one of many SDK 's “help doc” MS puts out here and there about DirectShow. I am suppose to build basic DirectShow application and use it as accessible debug library. I must be dense, but I cannot figure how to do it.
I do not need full blown sample code, there are plenty of them here, but gentle nudge into right direction in building from SDK sample would be appreciated.
Thanks for your time.
Two reasons for this update.
Soren, I did not delete my last post, I guess gremlins at work.
Second, I am making progress using DirectShow, however, I just got past enumerating video devices and still struggling with DirectShow overall concept.
I just love MS inventing all these therms with very terse explanations – graph, filter , bag, moniker etc.
Old fashioned flow chart would IMHO work much better than MS one pages samples which are not tied together.
The most confusing are the VMR options – windowless or with window?
And when you do search all you get is reference to Window7, back paddling to XP as I do is inevitable.
But eventually I'll get
Thanks for your help.
which is a picture control, it type property has beent set to "Frame". So it will act as a frame to the bitmap positioned on the dialog.
Or else plz give me any suggestion if we can stretch a bitmap.
Whenever I change the resolution of the PC, I want to change the size of the bitmap accordingly. I can change the position and size of the controls, but prob is with the Bitmaps, BMP size I can't change. So I was looking out any way for this.
Last Visit: 31-Dec-99 18:00 Last Update: 1-Oct-23 21:46