Polygon Reduction->CurrentStateToObject

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/09/2007 at 19:47, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   R8.2-R10 
Platform:   Windows  ; Mac  ;  Mac OSX  ; 
Language(s) :     C++  ;

---------
I'm sort of in a quandry here. When done manually, adding a Polygon Reduction deformer, waiting for it to do the calculations, and then doing CurrentStateToObject works. When done programmatically, I don't always get what I want and this appears to be related to how long the Polygon Reduction takes to do its work and the execution of my code.

So, is there any way to wait on something that would indicate that the Polygon Reduction deformer has finished doing its work before commencing with CurrentStateToObject (SendModelingCommand())?

Thanks!

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/09/2007 at 20:12, xxxxxxxx wrote:

Hmmm. I see that Polygon Reduction eventually returns MSG_POINTS_CHANGED and MSG_POLYGONS_CHANGED - sort of expected and hoped for. Soooo, if I set a mode flag to separate my process from any others, it can wait and continue. The problem is 'continuing'. This makes the method/code layout a bit treacherous stopping a linear routine (setting undos and whatnot) at one point and then starting the process up again later. Fun!

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/09/2007 at 21:25, xxxxxxxx wrote:

Hmmm, again.

It seems that when the MSG_POLYGONS_CHANGED arrives, it is on a copy of the original. Working with this doesn't appear to be very fruitful in the CurrentStateToObject phase.

How would I get around this? I tried storing the original tag (to get at the original object). That works - if you want CSTO of the original geometry - not! I want a CSTO of the reduced geometry. Maybe GetDeformCache() is called for here?

It would have been much easier if my linear process could 'wait' inline on the Polygon Reduction deformer instead of this long winded approach - eh hem...

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/09/2007 at 22:34, xxxxxxxx wrote:

Okay. Nevermind...

So the original method works. The fault lies in how I'm restoring the figure to 'default pose' - if morphs are controlled by other 'dials', they are zeroed, unfortunately. Not much to do to avoid this for what is being done - don't ask!