#54 GLE functions have no effect

v2.0
closed-fixed
GLE (4)
6
2003-05-03
2003-01-07
Mike C. Fletcher
No

This demo just shows a blank screen with 2.0.1 builds
of PyOpenGL on both Python 2.2 and 1.5.2.

Discussion

    • labels: 338830 --> GLE
     
  • Logged In: YES
    user_id=34901

    This appears to be a more general problem, all of the
    following have no effect:
    gleTwistExtrusion,
    gleExtrusion,
    glePolyCylinder. Tests demonstrating problem are:
    twburton/knots and GLE/texas as well as the (non-public
    twist2.py demo).

     
    • priority: 3 --> 6
    • assigned_to: nobody --> mcfletch
    • summary: GLE/texas demo doesn't show anything --> GLE functions have no effect
     
    • status: open --> closed-fixed
     
  • Logged In: YES
    user_id=34901

    Fixed, the demos now work. There's some strange problem
    remaining with glePolyCylinder when a full loop is created
    :( . Not sure what causes it, but it actually can crash the
    app (segfault) if you include the start-point in the
    subsequent-points set (I think I'll open a new bug for that).

    Note that the problems were even more widespread than the
    last not mention, as there were similar problems in most of
    the functions, we just don't have tests for them :( , all
    were a result of the switch to the newer SWIG (the GLE code
    uses the d_0_1 style macros for getting the lengths of other
    arguments, and those changed semantics, but not form, across
    the swig versions).