BaseContainer::GetDirty() doesn't always change in C4D 2024

[fwilleke80]

Hi,

I noticed that, in C4D 2024, the return value of BaseContainer::GetDirty() does not always change after changing a value in the container. Is this a bug? I am using BaseContainer::GetDirty() to detect changes to a container, and now this doesn't work anymore.

How can I detect changes to a BaseContainer in C4D 2024?

If a fairy granted me three wishes, I would greatly appreciate the addition of functions like BaseContainer::GetHashCode(), GeData::GetHashCode(), and a standard way to implement a GetHashCode() function for CustomDataTypes (which would be invoked by GeData::GetHashCode()).

Cheers,
Frank

[ferdinand]

Hello @fwilleke80,

thank you for reaching out to us.

I noticed that, in C4D 2024, the return value of BaseContainer::GetDirty() does not always change after changing a value in the container. Is this a bug? I am using BaseContainer::GetDirty() to detect changes to a container, and now this doesn't work anymore.

While this certainly sounds like a bug, without something more concrete we can do nothing to help you here. Which parameter types have been changed? The context somewhat implies that this does happen when writing custom data types? We will need code to do anything concrete here.

If a fairy granted me three wishes, I would greatly appreciate ...

I think the problem with both are custom data types and that our tech team is probably a bit reluctant to rely for collision resistance on external developers (when we would offer a CustomDataTypeClass::GetHashCode). We could of course implement it and then not use it ourself, but that is not how we tend to do things.

Cheers,
Ferdinand