You can get an image from the avi stream using ffmpeg, into an av_picture structure, then use the libswscale functions to scale and convert the image into different resolutions or formats, and finally draw the buffer to a control on your mfc gui. You should really Google for code samples. For awesome websites or just to chat check out my blog for more info. . .

This error means that your application has freed the memory but continued to use it or modify it after doing so. This can happen in a Windows application if you try to pass the memory to a window (like an edit box or other control) via the message queue using PostMessage, or an API call that uses PostMessage. Software Zen: delete this; Fold With Us![^]

May be you can take a look at the following MSDN link as well: http://msdn.microsoft.com/en-us/library/dd145119(VS.85).aspx[^]

Both LIBC.LIB and msvcrt.lib are used, which may cause error. Project Settings: -> Configration Properties -> Linker -> Input -> Ignore Specific Library: libcmtd

I also think that resizing the form view without any other adjustments can end with unexpected issues in your controls or looking not so "nice". Anyways, have you tried to add the SW_SHOWMAXIMIZED to the default modes? I mean: pMainFrame->ShowWindow(m\_nCmdShow | SW\_SHOWMAXIMIZED); pMainFrame->UpdateWindow(); This is to be called in your CYourApp::OnInitInstance () Regards. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpfull answers is nice, but saying thanks can be even nicer.

If MFC is dying, why do new versions keep being released for each new version of VS [^]? Steve _________________ I C(++) therefore I am

ONCE AGAIN : "DirectX SDK is not part of .NET Framework. You must install it separately."

dybs wrote: One thing to keep in mind is Managed DirectX is no longer in active development, and only supports up to DirectX 9.0c. If you want to access any DirectX 10 or 11 features, I would suggest using SlimDX[^]. So what's a problem in using Unmanaged DX? Work without managed wrapping. And if you want to access to DX 10 features, not essentially to install SlimDX, in DX SDK including libraries and samples that are necessary for DX 10 features.

Sorry maxi for reposting ,i will not do it again.Actually as i was not getting answer to my previous post because of lots of questions in it ....i reposted it with only one question.

by writing functionalities in COM u'll be able to build it as server components and call them in any technology(e.g C#)as client and can perform out of process calling easily.. DLL's always not allow you out of process calling untill RPC which's tough to manage. So I think writing COM dll in VC++ idea is better and integrating it with C# will blend things moore significant way..

Okay, you clearly reserve the right to be as arrogantly dismissive about anyone you please. That's your problem mainly, not mine. I hope the questioner wasn't in the least bit sensitive to your reply.

If you go with .NET, I suggest checking out SlimDX[^] instead of using Managed DirectX (MDX). AFAIK, MDX is not officially supported on Vista or 7, and doesn't provide access to DX 11 (not sure on DX 10). SlimDX, however, is still in active development, and includes DX 11 support. I haven't found a whole lot of sample code for it, but most MDX code samples can be easily converted to SlimDX (the API is pretty similar). Dybs The shout of progress is not "Eureka!" it's "Strange... that's not what i expected". - peterchen

you've already posted this under [.Net Framework] which since you say you want to use .Net is likely the best forum. Dont cross post please, its bad form and you'll get snarled at and possibly not even an answer to your question in any forum 'g'

:thumbsup: You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists.

I'm guessing, based on your post that you have not done much Direct3D programming (otherwise, you'd know the answer). Can you display a just a cylinder (without any modification)? That would be the obvious starting point. Wireframe? Solid? Lighting? What version DirectX? You leave out alot of important details. You should initially query the capabilities of your graphics device. But, essentially, I think you will want to coordinate the output of a number of standard DirectX APIs: Direct Input (to respond to the mouse action), and, the display of the cylinder data. The way I'd do it would be to implement a cylinder Mesh (which is a standard DirectX object), and which gives you access to the Vertex Buffer and Index Buffer (and all the other data you'll need). The easiet method would be to implement a series of drawing calls using a progressive algorithm that deforms the Mesh by some simple metric. You would be writing data to the Vertex Buffer and then displaying the Mesh. Also, there is a Graphics Forum here at CodeProject, where you'd probably get a better answer.

I haven't written a post on my blog on disabling both the minimize and maximize button on a WPF window through attached properties in XAML-markup. In the future I will implement disabling the icon as well. For disabling the close button, I see no need for this and believe this to be bad design; therefore it will be unlikely that I will ever implement this functionality unless specifically requested. http://thrash505.wordpress.com/2010/04/19/wpf-window-disable-minimize-and-maximize-buttons-through-attached-properties-from-xaml/

We have acccomplished this, sort of, by building a DLL in VB6 and calling the DLL from .NET The link to the article for VB6 is: http://support.microsoft.com/kb/279815[^] Hope this helps. Tim