From: Marcin Romaszewicz (marcin++at++asmodean.engr.sgi.com)
Date: 11/15/2001 17:18:13
On Thu, 15 Nov 2001, Ive Akkermans wrote:
> hi performers,
>
> Quite quickly, but the bounding-box problem is already solved ! Again
> it's something you would NOT have expected. What I needed to do to keep
> the object from disappearing, was add a setBound(NULL, PFBOUND_DYNAMIC)
> for the object, for every frame. I'd say, ridiculous !
>
You must be doing something wrong. When you change the transformation on a
DCS, its bounding box and the bounding boxes of all its parents will be
recomputed. This is one of those parts of Performer that pretty much every
existing performer app exercieses, and bugs such as these were flushed out
a long time ago. Are you subclassing pfDCS and replacing some of its
functions? How are you changing the transformation? Is this related to the
problem you were having with pfDCS::setCoord in your pfDCS subclass?
-- Marcin
> But it works, that's what counts :)
>
> So, anybody knows why _this_ happens ? Known problem / bug ?
>
> Strangely enough, when the new coordinate is set twice, the bounding box
> is set correctly the second time (not after the 1st!) ! Seems like the
> dcs node is a bit 'deaf' :-)
>
> greetings,
>
> ive.
>
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
>
This archive was generated by hypermail 2b29 : Thu Nov 15 2001 - 17:18:16 PST