Capturing the right display, but rendering to the wrong one.

  • I'm trying to modify the Performer Application in the developer
    examples to capture a secondary display if it's attached, and then
    render to it. I can capture the secondary display, but the qtz file
    still renders to the main display. I think it has to do with the
    openGL Context that I'm creating, but I don't know what to change to
    fix it. The code is attached. I'm sure the solution is simple, I just
    can't figure out what it is. Thanks for your time.

    Namaste,
    Karan
    
  • On Sep 15, 2007, at 4:25 PM, Karan Lyons wrote:

    > I'm trying to modify the Performer Application in the developer
    > examples to capture a secondary display if it's attached, and then
    > render to it. I can capture the secondary display, but the qtz file
    > still renders to the main display. I think it has to do with the
    > openGL Context that I'm creating, but I don't know what to change
    > to fix it. The code is attached. I'm sure the solution is simple, I
    > just can't figure out what it is.

    This would probably get a better answer from the quartzcomposer-dev
    list, but I think the issue might be related to other multi-context
    issues that are known in Quartz Composer on 10.4. It would help if
    you could file a bug on this and send me the bug number.
    --
    David Duncan
    Apple DTS Quartz and Printing
    <david.duncan...>
  • On Sep 17, 2007, at 11:56 AM, Karan Lyons wrote:

    > Thankyou, but I don't think it's an issue with Quartz Composer.
    > I'm pretty sure that it's an issue with the code I modified,
    > specifically the way the openGL context is created. I've attached
    > the project as a zip file to this email if anyone wants to look at
    > the whole thing. To see the issue you need to have at least two
    > monitors.
    > What should happen is that the application will run, the secondary
    > monitor will blank out, and the primary monitor will show the
    > "Rings" composition from the developer examples. As the primary
    > screen has not been captured, there will be a lot of screen
    > refreshing issues.
    > If there's any more information you need, I'll be more than happy
    > to supply it.
    >

    It looks like your setting up your attributes array before you
    discover what display ID the secondary display is. Try updating your
    attributes array (and delaying the corresponding creation of the
    pixel format) until after you've discovered the ID of the secondary
    display.
    --
    David Duncan
    Apple DTS Quartz and Printing
    <david.duncan...>
previous month september 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today