posted 07-27- 06:41 AM               

PARENT
child

1. Fires which start in the parent did NOT affect the child in any way

2. Fires which start in the child do affect the parent

3. You can use "obNoDamageChain" in the proplist of the child and teh parent would get NOT damaged by the fire started in the child

-> OPSpecification page 22 : "obNoDamageChain - Some fraction of damage to me is normally also passed up to my parent. This property inhibits this behavior."

This makes me thinking, and I think now :

4. The parent gets not damaged by the fire from the child itself, it only receives some "fractional" damage from the child (see 3.)

5. So logically, making the parent FireResistant would change absolutely nothing, when the fire comes from the child (see 4.), You had to take care of the FireResistance of the child, to regulate the "fractional damage" which is send to the parent !

6. Forget the Specification of obFireResistant from the OP-Spec. page 22 ("...The optional number is the fraction of normal object resistance (range: 0-1). 1 means same as normal, 0 means impervious to fire...") Might be this is not wrong at all, but I thought so far we can only use values from 0 to 1 (0.2, 0.4 etc). Anyway you can use any number and the "range" is the fraction of 1/number. So if we use obFireResistant 2 the damage send to the parent is 1/2 of the normal value...

I tested it and it does work fine ! But I'm not sure what to do when the fire starts in the object itself (i.e. my "fireparent" did not get any obDamage or inertia properties, so I don't had to take care of damage here), might be that obFireResistant works the same way.

Hope this helps someone - any questions ?

LK

posted 07-27- 08:09 AM               

------------------
-Sv =FC=

WWI in SDOE!