jogl
  1. jogl
  2. JOGL-164

Expose render-to-texture target

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: jogl
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      164

      Description

      The current render-to-texture functionality allows a Pbuffer to be bound to either
      GL_TEXTURE_2D or GL_TEXTURE_RECTANGLE_NV (based on the value of
      offscreenRenderToTextureRectangle set in the GLCapabalities object). However,
      in some cases, the resulting texture target may not be what the programmer
      expects (eg. if GL_TEXTURE_RECTANGLE_NV is not available). By adding an
      accessor to GLPbuffer (and, hence to GLPbufferImpl as well as GLContext and all
      its subclasses), the actual texture target being used could be made available to
      the API programmer.

      Issue 163 refers to an implementation that also includes an implementation of
      this feature.

        Activity

        Hide
        kbr added a comment -

        Thanks for the suggestion and patch. However, the OpenGL community is moving
        away from pbuffers and toward the frame buffer object extension, which is a more
        portable and higher-performance solution for offscreen rendering than pbuffers.
        I'm therefore reluctant to enhance JOGL's pbuffer implementation significantly
        at this time, because we're trying to stabilize the final release of the current
        JOGL APIs. Your patch will be considered for a future version of JOGL
        implementing the JSR-231 APIs.

        Show
        kbr added a comment - Thanks for the suggestion and patch. However, the OpenGL community is moving away from pbuffers and toward the frame buffer object extension, which is a more portable and higher-performance solution for offscreen rendering than pbuffers. I'm therefore reluctant to enhance JOGL's pbuffer implementation significantly at this time, because we're trying to stabilize the final release of the current JOGL APIs. Your patch will be considered for a future version of JOGL implementing the JSR-231 APIs.

          People

          • Assignee:
            jogl-issues
            Reporter:
            tedmunds
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: