On 02/11/2015 at 10:22, xxxxxxxx wrote:
User Information:
Cinema 4D Version: 16+
Platform: Windows ; Mac ; Mac OSX ;
Language(s) : C++ ;
---------
Hi,
is there a list or something that shows what the DocumentInfoData::data pointer should be cast to according to each message type? The docs are silent about this just saying that this depends on DocumentInfoData::type.
Thanks
On 02/11/2015 at 10:26, xxxxxxxx wrote:
I am interested to know the same for MessageFilter::data as well. Same issue.
Thanks
On 03/11/2015 at 03:22, xxxxxxxx wrote:
Hi,
Originally posted by xxxxxxxx
Is there a list or something that shows what the DocumentInfoData::data pointer should be cast to according to each message type? The docs are silent about this just saying that this depends on DocumentInfoData::type.
In the documentation for DocumentInfoData::type there's a link to MSG_DOCUMENTINFO_TYPE enum.
In this enum list data is only mentionned for these 2 DocumentInfo messages:
For MSG_DOCUMENTINFO_TYPE_BEFOREMERGE data points to a MSG_DOCUMENTINFO_TYPE_BEFOREMERGE_RESULT enum.
As for MSG_DOCUMENTINFO_TYPE_MAKEPROJECT the documentation isn't accurate: data actually points to a DocumentInfoMakeProj struct (contains the source and destination files plus allow copy and GUI states).
Originally posted by xxxxxxxx
I am interested to know the same for MessageFilter::data as well. Same issue.
MessageFilter::data is basically the same as the data parameter in NodeData::Message() for all other messages except this one. The pointed data depends on the MSG MessageFilter::type.