MSG_UPDATE?

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

On 10/01/2009 at 20:00, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   9.1+ 
Platform:   Windows  ; Mac  ;  Mac OSX  ; 
Language(s) :     C++  ;

---------
Howdy,

The SDK documentation says:

> Must be sent if the bounding box has to be recalculated.
> (Otherwise you can use MSG_CHANGE.)

But there is a problem sending MSG_UPDATE to an object from the TagData::Execute() function (expression tag) when in any of the edit modes and using the Knife tool. When the TagData::Message() function receives the message MSG_POINTS_CHANGED along with a VariableChanged structure, the vc->new_cnt is not correct. If I comment out the line:

> //op->Message(MSG_UPDATE);

... in the TagData::Execute() function, then the vc->new_cnt is correct.

Is this a bug, or are there special rules on when you can send MSG_UPDATE to an object?

Adios,
Cactus Dan

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

On 15/01/2009 at 04:00, xxxxxxxx wrote:

Sorry, I can't confirm this, it works correctly here. Which Cinema version are you using currently, does it matter which version?

cheers,
Matthias

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

On 15/01/2009 at 10:08, xxxxxxxx wrote:

Howdy,

I've tested this in R9, R10 and R11 Demo.

It only happens when you single click each point to form a cut line.

If you drag a cut line it seems to work normally

When I comment out the line:

> //op->Message(MSG_UPDATE);

... then the single click method works as expected.

Adios,
Cactus Dan

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

On 16/01/2009 at 01:28, xxxxxxxx wrote:

Ok, I tested it again exactly as you described. Still the 'old_cnt' and 'new_cnt' are correct. But there is indeed something strange going on with the knife tool. The single click method creates just one new point when it should create two new points as you show in your pictures. I will report it to the developers.

cheers,
Matthias

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

On 16/01/2009 at 08:08, xxxxxxxx wrote:

Howdy,

OK, sorry. Yes the old and new point counts are actually correct, because the first point isn't being created. That's actually what meant to say. :o(

My plugin still works fine without sending MSG_UPDATE, so I will leave that line commented out for now. ;o)

Adios,
Cactus Dan