Re: pfPassChanData :-(
John Rohlf (jrohlf++at++tubes)
Fri, 22 Sep 95 16:59:06 PDT
>
> Hi Performer-people,
>
> In my application pfPassChanData() doesn't seem to be doing quite what it
> should :-( I have two modes which I can toggle between with the hit of a
> key:
>
> Mode 1:
> Channel 1: Calls pfDraw() once.
> Channel 2: Turned off.
>
> Mode 2:
> Channel 1: Calls pfDraw() once.
> Channel 2: Calls pfDraw() twice.
>
> When I hit the key, the chan-data for channel 1 changes and I call
> pfPassChanData() to make sure it gets sent down the pipeline to the DRAW
> process. However I am printing out the value of the data passed to my draw
> call-back (from within that call-back) and after a few hits of the key, it
> starts changing between the value it should have (for the current mode), and
> the value it should have in the other mode. I have a printf at every call
> to pfPassChanData(), so I know it is NOT being called unless I hit the key,
> but still the data being passed to the draw call-back is oscillating between
> two different values. It is as if Performer is still using an older copy of
> the chan-data sometimes, rather than the new one I asked to pass down.
>
This is a bug in 1.2 which may be exacerbated by disabling
channel 2. For now, call pfPassChanData each frame until you get 2.0.
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:51:54 PDT