correct init of InExcludeData
On 19/11/2013 at 03:39, xxxxxxxx wrote:
i stock here on a basic thing
what is the correct term to init a InExcludeData ?
def Init(self, op) : bc = op.GetDataInstance() bc.SetInt32(c4d.CLASSES_INEX_ACTIVE, 0) return True
On 19/11/2013 at 06:35, xxxxxxxx wrote:
Your question is a bit misleading (at least for me). You are asking how to initialize a
InExcludeData (instance), where the answer would be :
_<_t_<__<_t_<__<_t_<__<_t_<__<_t_>_Parameters:| v ([
InExcludeData](file:///E:/Misc/SDK%20Help/C4d%20SDK%20Documentation%20Python/help/modules/c4d/CustomDataType/InExcludeData/index.html#c4d.InExcludeData)) – Copy constructor.
Return type:| [
Returns:| Notable is here IMHO that while v is optional, you are well advised to always pass
existing data from the gui-element you are working on/for as a parameter, or strange
things might happen.
Your posted code on the other hand suggests that you are looking for the correct way
to initialize a InExclude property / field for a NodeData instance. It is not mandatory to
use NodeData.InitAttr(), but especially for more complex data types it actually is in the
end. There are some problems with InitAttr() (for example with the the FontData type,
which is initialized as TimeDateData), but I have never had problems with InExcludeData.
The code would be something like that :
self.Initattr(op, c4d.InExcludeData, c4d.SOMEID)
I am not sure why you are using that backwards way with the data instance. Is that
because of the newly introduced types with R15 ? I have not dealt with them yet, so
I cannot say anything about them, but I also do not see why these are a of
importance here, as they actually target numeric types.
On 19/11/2013 at 06:57, xxxxxxxx wrote: