• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]


  • Subject: Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
  • From: "Sean McBride" <email@hidden>
  • Date: Fri, 3 Jun 2005 13:38:55 -0400
  • Organization: Rogue Research

On 2005-06-03 10:27, Andy O'Meara said:

>Another version of expressing my goal is: whatever method Apple internally
>uses to get QuickTime frames ultimately to NSViews is what I'd also like to
>do (ie, QT frames ultimately originate in CPU RAM and can be arbitrarily
>large, so what is Apple doing to maximize performance and get them to the
>screen?).  In the wonderful world of Classic/Carbon, CopyBits() was the
>ticket, but now of course that's all going away.  By the same token,
>CPU-based frame rendering folks like me are a dying breed (and being
>replaced by openGL folks), so there's not a lot of us out there now.  My
>company has new visuals in the works (on OpenGL), but it'd be nice to use
>G-Force and WhiteCap in Cocoa for stuff like Screensavers and so on.
>
>It'd be nothing to have my engine's output to some other frame buffer--is
>there any high-performance/low-overhead way to get a frame buffer that's
>going at the order of 30fps to a NSView? (ie, is there a secret replacement
>for an offscreen GWorld such that I get get frames to the screen under Cocoa
>rapidly? -- I'm pretty sure no). -- I'm dying to know what Apple does for
>QuickTime frames.

I'm far from an expert, but I'd say the answer is OpenGL.  I would
definitely suggest ditching GWorlds and anything QuickDraw!!

The secret replacement to an offscreen gworld I guess is an
NSBitmapImageRep.  Then you can take that and put it in an OGL texture:
<http://developer.apple.com/samplecode/NSGLImage/NSGLImage.html>

Also, OpenGL screensaver example:
<http://developer.apple.com/samplecode/OpenGL_Screensaver/
OpenGL_Screensaver.html>

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update] (From: glenn andreas <email@hidden>)
 >Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update] (From: "Andy O'Meara" <email@hidden>)

  • Prev by Date: Re: CoreData: Using willSave to update timestamps causes hang?
  • Next by Date: Re: Custom objects in drag pasteboard? [solved]
  • Previous by thread: Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
  • Next by thread: Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
  • Index(es):
    • Date
    • Thread