FROM : dan sinclair
DATE : Tue May 13 23:02:14 2008
I was playing a bit with Cocoa and full screen and I wrote a quick blog
entry about it: http://everburning.com/news/going-fullscreen-with-medium/
I'm not sure if it's the correct way, or the best way, but it does seem to
work for me (although I believe it will limit the OS version you can run
under).
dan
On Tue, May 13, 2008 at 1:40 PM, Dennis Munsie <<email_removed>> wrote:
> In this case, what I am trying to accomplish is something along the
> lines of how Keynote and Powerpoint behave. I only want to take over
> one display, most likely connected up to a projector. But, I also
> occasionally want to have it in a window. I'm not expecting any
> controls to work -- this is strictly a view-only window.
>
> Also -- the code currently works just fine for the case of a single
> display machine or when the window is on the main display. I just
> need to make it work when the window is on another display.
>
> thanks!
> dennis
>
> On Tue, May 13, 2008 at 4:23 PM, Ricky Sharp <<email_removed>> wrote:
> >
> >
> > Ack. Do not expect to use AppKit with a captured display. I really
> wish
> > all those archived code examples out there would just vanish; just leads
> to
> > more folks doing this.
> >
> > Anyhow, if you really must capture the display using the CG APIs,
> please
> > note that there's different mechanisms for getting data onto the screen.
> > Search cocoa-dev and quartz-dev for the details on why you cannot use
> AppKit
> > with captured displays.
> >
> > If you must use AppKit, you can always use a call to SetSystemUIMode
> (to
> > hide menu bar and dock). Then, enumerate all screens and put up
> "blanking"
> > windows on each one. Then, put up your "content" window over a
> particular
> > blanking one. See the child window APIs for how you can ensure that the
> > content window is never brought forward over the blanking one.
> >
> > This latter approach is what I've done for the past few years and has
> > worked great.
> >
> > ___________________________________________________________
> > Ricky A. Sharp mailto:<email_removed>
> > Instant Interactive(tm) http://www.instantinteractive.com
> >
> >
>
>
>
> --
> dennis
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
DATE : Tue May 13 23:02:14 2008
I was playing a bit with Cocoa and full screen and I wrote a quick blog
entry about it: http://everburning.com/news/going-fullscreen-with-medium/
I'm not sure if it's the correct way, or the best way, but it does seem to
work for me (although I believe it will limit the OS version you can run
under).
dan
On Tue, May 13, 2008 at 1:40 PM, Dennis Munsie <<email_removed>> wrote:
> In this case, what I am trying to accomplish is something along the
> lines of how Keynote and Powerpoint behave. I only want to take over
> one display, most likely connected up to a projector. But, I also
> occasionally want to have it in a window. I'm not expecting any
> controls to work -- this is strictly a view-only window.
>
> Also -- the code currently works just fine for the case of a single
> display machine or when the window is on the main display. I just
> need to make it work when the window is on another display.
>
> thanks!
> dennis
>
> On Tue, May 13, 2008 at 4:23 PM, Ricky Sharp <<email_removed>> wrote:
> >
> >
> > Ack. Do not expect to use AppKit with a captured display. I really
> wish
> > all those archived code examples out there would just vanish; just leads
> to
> > more folks doing this.
> >
> > Anyhow, if you really must capture the display using the CG APIs,
> please
> > note that there's different mechanisms for getting data onto the screen.
> > Search cocoa-dev and quartz-dev for the details on why you cannot use
> AppKit
> > with captured displays.
> >
> > If you must use AppKit, you can always use a call to SetSystemUIMode
> (to
> > hide menu bar and dock). Then, enumerate all screens and put up
> "blanking"
> > windows on each one. Then, put up your "content" window over a
> particular
> > blanking one. See the child window APIs for how you can ensure that the
> > content window is never brought forward over the blanking one.
> >
> > This latter approach is what I've done for the past few years and has
> > worked great.
> >
> > ___________________________________________________________
> > Ricky A. Sharp mailto:<email_removed>
> > Instant Interactive(tm) http://www.instantinteractive.com
> >
> >
>
>
>
> --
> dennis
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
| Related mails | Author | Date |
|---|---|---|
| Dennis Munsie | May 13, 19:11 | |
| Ricky Sharp | May 13, 22:23 | |
| Dennis Munsie | May 13, 22:40 | |
| John Stiles | May 13, 23:00 | |
| dan sinclair | May 13, 23:02 | |
| Dennis Munsie | May 13, 23:47 | |
| Jean-Daniel Dupas | May 14, 00:30 | |
| Dennis Munsie | May 14, 05:30 | |
| Jean-Daniel Dupas | May 14, 09:56 | |
| Sean McBride | May 14, 18:54 | |
| Mike Fischer | May 16, 18:18 |






Cocoa mail archive

