Re: Fullscreen on secondary displays
Re: Fullscreen on secondary displays
- Subject: Re: Fullscreen on secondary displays
- From: "Dennis Munsie" <email@hidden>
- Date: Tue, 13 May 2008 17:47:10 -0400
Other than me wanting to avoid re-writing my view drawing code? :)
I will probably look into doing this -- of the unanswered questions
that I have is will I be able to toggle (relatively) easily between a
full-screen context and a windowed context? Do I need to completely
throw out my NS* drawing code? Or can I legitimately get away with
throwing out my NSWindow and NSView usage while in fullscreen mode?
Part of this stems from the fact that this is only a personal use app
right now -- so I'm not necessarily tied to the right way of doing
things at the moment. If I decide to distribute this in any way, I
would be all for ripping things out and re-writing as necessary. But
right now, I just need to have something working on my laptop only :)
thanks!
dennis
On Tue, May 13, 2008 at 5:00 PM, John Stiles <email@hidden> wrote:
>
> None of this really refutes what Ricky posted.
> You are just lucky that it works in the one-display case. It really isn't
> designed to work, and on some configurations, it just won't.
> Is there anything preventing you from following Ricky's advice?
>
>
>
>
> Dennis Munsie 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@hidden> 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@hidden
> Instant Interactive(tm) http://www.instantinteractive.com
>
>
>
>
>
>
>
--
dennis
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden