Re: [info-performer] pfGetCurLights in Performer 3.0 Windows

From: Alexandre Naaman (naaman++at++laplace.engr.sgi.com)
Date: 01/09/2003 17:00:09

• Next message: Alexandre Naaman: "Re: [info-performer] Using Qt and Performer API - Redefinition of 'ulong'"
• Previous message: Allan Schaffer: "[info-performer] info-performer now runs majordomo"
• In reply to: Guillaume Millet: "Re: [info-performer] pfGetCurLights in Performer 3.0 Windows"

On Thu, 9 Jan 2003, Guillaume Millet wrote:

> Hello,
>
> When trying to make my own pfGetCurLights function, I saw that there is the same
> problem with pfGetCurGState();
> I think there is the same problem with all C function of C++ API (pfGetCur* and more).
>
> Greetings
>
>

Hi Guillaume,

 You're correct, it looks like we missed exporting almost twenty pfGetCur*
functions. They are:

        pfGetCurCtab
        pfGetCurDList
        pfGetCurFog
        pfGetCurGState
        pfGetCurIndexedGState
        pfGetCurGStateTable
        pfGetCurHlight
        pfGetCurLPState
        pfGetCurLights
        pfGetCurLModel
        pfGetCurMtl
        pfGetCurSprite
        pfGetCurState
        pfGetCurStats
        pfGetCurTex
        pfGetCurTEnv
        pfGetCurTGen
        pfGetCurTLOD
        pfGetCurVChan

 Most of the C api is automatically generated and hence is properly
exported. What doesn't fall into this broader category was done manually
but it looks like we missed "a few"...

A+,

Alex.

• Next message: Alexandre Naaman: "Re: [info-performer] Using Qt and Performer API - Redefinition of 'ulong'"
• Previous message: Allan Schaffer: "[info-performer] info-performer now runs majordomo"
• In reply to: Guillaume Millet: "Re: [info-performer] pfGetCurLights in Performer 3.0 Windows"

This archive was generated by hypermail 2b29 : Thu Jan 09 2003 - 17:00:21 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.