Hi Mitch, Not sure of the exact methods to call - I have set breakpoints at various DirectDraw locations within ripping programs, and had the breakpoints hit when an image was being captured. The names in the DirectDraw symbols are fairly managed, but the call stack looks something like a call to IDirectDraw3::GetSurfaceFromDC, and then memory copying using the Lock method of Surface. These interfaces are depreciated, and I'm not sure if Direct3D surfaces are a replacement. Any DirectX gurus out there?
Nick ----- Original Message ----- From: "Mitch Denny" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 18, 2002 5:21 PM Subject: Re: [DOTNET] Screen capturing in dotnet > Nick, > > Thanks for the info. Have you seen any straight-forward > video ripper code for DirectX in C. I prefer > straight-forward C API calls over COM interop :) > > Ofcourse if you have an example in C# that would be > great too, or some pointers. > > ---------------------------------------- > - Mitch Denny > - [EMAIL PROTECTED] > - +61 (414) 610-141 > - > > -----Original Message----- > From: The DOTNET list will be retired 7/1/02 > [mailto:[EMAIL PROTECTED]] On Behalf Of Nick Wienholt > Sent: Tuesday, 18 June 2002 08:17 > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Screen capturing in dotnet > > > Hi Mitch, > > Commercial video rippers (which have pretty good screen capture > performance) use either DirectDraw (locking a DirectDraw surface), or > the same technique in the sample code you previously posted. DirectDraw > typically give the better performance. > > Nick > > ----- Original Message ----- > From: "Mitch Denny" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, June 17, 2002 6:48 PM > Subject: Re: [DOTNET] Screen capturing in dotnet > > > > Richard, > > > > Thanks, but Eric's code exhibits the same problem as those int he code > > > sample. When BitBlt is executed you get a fairly signigicant lock-up > > in the UI for a few moments. I've been trying to figure out how other > > tools do it, and all I can think of is that they take the screen bit > > at a time so that the lock up isn't as noticeable. > > > > That would tally with what I have seen (performance and behaviour > > wise) in certain tools. > > > > ---------------------------------------- > > - Mitch Denny > > - [EMAIL PROTECTED] > > - +61 (414) 610-141 > > - > > > > -----Original Message----- > > From: The DOTNET list will be retired 7/1/02 > > [mailto:[EMAIL PROTECTED]] On Behalf Of Richard Birkby > > Sent: Monday, 17 June 2002 18:14 > > To: [EMAIL PROTECTED] > > Subject: Re: [DOTNET] Screen capturing in dotnet > > > > > > Have a look at this: > > http://www.gotdotnet.com/userarea/filedetails.aspx?FileName=Win32windo > > w. > > zip > > > > > -----Original Message----- > > > From: The DOTNET list will be retired 7/1/02 > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Mitch Denny > > > Sent: 17 June 2002 09:00 > > > To: [EMAIL PROTECTED] > > > Subject: Re: [DOTNET] Screen capturing in dotnet > > > > > > > > > Gunasekaran, > > > > > > I did some early fiddlng with this and some success, although it > > > wasn't as neat or as fast as I would have liked. Do a search for > > > "screen capture" in the message archives, they include all the > > > relevant discussion and sources. Please do let me know if you can > > > get it running fast and without locking the screen. > > > > > > http://discuss.develop.com/dotnet.html > > > > > > Hope this helps. > > > > > > ---------------------------------------- > > > - Mitch Denny > > > - [EMAIL PROTECTED] > > > - +61 (414) 610-141 > > > - > > > > > > -----Original Message----- > > > From: The DOTNET list will be retired 7/1/02 > > > [mailto:[EMAIL PROTECTED]] On Behalf Of Gunasekaran Swamy > > > Sent: Monday, 17 June 2002 15:22 > > > To: [EMAIL PROTECTED] > > > Subject: [DOTNET] Screen capturing in dotnet > > > > > > > > > Hi All, > > > > > > Is there any provision to capture the screenshots in > > > Dotnet .If any API exists .Pls let me know . > > > > > > Thanks in advance > > > Guna > > > > > > You can read messages from the DOTNET archive, unsubscribe from > > > DOTNET, or subscribe to other DevelopMentor lists at > > > http://discuss.develop.com. > > > > > > You can read messages from the DOTNET archive, unsubscribe from > > > DOTNET, or subscribe to other DevelopMentor lists at > > > http://discuss.develop.com. > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.370 / Virus Database: 205 - Release Date: 05/06/2002 > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.370 / Virus Database: 205 - Release Date: 05/06/2002 > > > > You can read messages from the DOTNET archive, unsubscribe from > > DOTNET, or subscribe to other DevelopMentor lists at > > http://discuss.develop.com. > > > > You can read messages from the DOTNET archive, unsubscribe from > > DOTNET, or subscribe to other DevelopMentor lists at > > http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, > or subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
