can you get a handle to the window and call InvalidateRect BOOL InvalidateRect( HWND hWnd, // handle to window CONST RECT* lpRect, // rectangle coordinates BOOL bErase // erase state );

Easiest thing to do is just catch all the WM_COMMAND messages with HIWORD (wParam) == BN_CLICKED in your WindowProc and decide which OnClick to call based on the LOWORD (wParam) which will be your button ID. Judy

It seems you have put also window controls onto view. Again, I prone to say that in that case the controls are also redrawn (not updated). This may take some time too. You should provide more info on what you are doing to let us to be more concrete. Anyway, you should update not entire view but a part of it. You'd rather set a mask parameter into UpdateAllViews and get it from CView::OnUpdate method, then update the necessary part of a view. -- ====== Arman

Will directshow is different from VFW API First it is com based, so no more flat API calls, just com objects Second, DirectShow framework depends upon waht is called a Graph and Filters. So I think what you need is to develop your own data stream filter (there is examples with directshow) and build a graph to capture from your stream filter to the avi file. Data Stream Filter ----> VIDEO ENCODER Filter (if any) ---> AVI MUX Filter ---> File Writer Filter. Hope this helps to figure out what reading you need in directshow to do your work Hesham

I would guess that it is tool large for the VirtualDub or some other associated program. Does it die when it hits approx 2.7G? If so they are probably using a signed 32 bit buffer somewhere.

It seems to me that you can't get 2 digits instead of 3. But you can print to string using sprintf() instead of printf(), find unnecessary '0' character and remove it.

Look at documentation on GetFileVersionInfo(), GetFileVersionInfoSize() and VerQueryValue() (to retrieve a VS_FIXEDFILEINFO structure). I never did it to retrieve the build number, but I suppose you have to find out which are the corresponding bits in the FileVersion or in the ProductVersion. Hope this helps, Paolo.

Well, the correct answer is 0. The assignment reduces to: j = j++; Since j++ evaluates to 0, 0 gets stuffed in j. This is really bad programming practice, though. I hope you don't plan on writing production code this way. ;)