Thank you Ferdinand! I'll continue in backstage with this topic. V.

Good to hear! And your question was not 'messy', but to ensure efficient support, we must enforce certain rules. Cheers, Ferdinand

Hello @wtools3d, @wtools3d said in ObjectData::GetDimension() ignored?: Maybe you could add some further explanation in the documentation where the overwritten bounding data is used in the cinema. Yes, this is a good idea, I will do that. Cheers, Ferdinand

Yes, this condition was the issue! It was a copy-paste part from some C4D example without deeper thinking. Now it works as expected also with animations! Regarding the value as a class parameter, it is of course handled for read-write copy. Our plugins are ported into more applications not just for C4D. Using its own data management so that's why the Get-Set callback are used. Thank you for your quick and useful help, as usual Regards, Viktor

Hello @WTools3D, without any further questions, we will consider this topic as solved by Tuesday, November the 2nd and flag it accordingly. Thank you for your understanding, Ferdinand

I guess it is probably not doable with current api. I am marking this as solved! I sacrifice the possibility that the generator can be changed to a Spline object with the Cinema Make Editable command. If the call to NurbsData::GetContour() returns null, no highlighting or geometry will be drawn. So I can draw everything without any collisions. Only downside of this is that additional command for conversion of this object to a spline object is needed. Thanks.

Thank you guys for quick reply. But I was probably not clear enough with the question. I do understated the concept of setting panel description via GetDDescription() callback. I already did the checks for whether it is request for full description of just single id. As it is listed in the example below (it is member function of C4dControls class from previous snippet void C4dControls::AddIntChoice(int id, int gid, const String& name, const BaseContainer& items) { const DescID cid = DescLevel(id, DTYPE_LONG, 0); //--------------------------------------------------------------------- if (ex_descr && (!ex_singleid || cid.IsPartOf(*ex_singleid, nullptr)) ) { BaseContainer bc = GetCustomDataTypeDefault(DTYPE_LONG); //--------------------------------------------- bc.SetInt32 (DESC_CUSTOMGUI, ID_QUICKTABSRADIO_GADGET); bc.SetString(DESC_NAME, name); bc.SetInt32 (DESC_SCALEH, 1); // animate OFF bc.SetInt32 (DESC_ANIMATE, DESC_ANIMATE_OFF); //--------------------------------------------- bc.SetContainer(DESC_CYCLE, items); //--------------------------------------------- ex_descr->SetParameter(cid, bc, DescLevel(gid)); } } But it is still calling to rewrite each control description several times after any event in GUI. What confuses me the most, is that each series of calls is with the different pointer to description (Description* description) For example there are five different pointers to description when ToolData::GetDDescription() is executed for the same event. (after mouse click into attribute manager) Is this the way how it really works? There are more versions of description for the same panel, and all of them have to be initialized repeatedly after each event? Thanks! Viktor

Works like a charm! It's much more flexible than I hoped;) Thanks a lot!

@m_magalhaes Thanks Manuel! When I fill-in only Inner edges in NgonBase::BuildNgon, then it surprisingly works I don't know why I tested all combinations except this one There are still some minor glitches, some inner edges are randomly not hidden, but ngons created are valid for all the cases I have tested. Random glitches are easily fixable with forcing all inner edges to be hidden. I will test it more, but this seems to be reliable for now. NGONS import - read outer edges directly from Pgon::*m_Edge array NGONS export - with NgonBase::BuildNgon(), filling Inner edges only, and force hide inner edges on quads. Thanks a lot Manuel, Your help has been very valuable to me. Regards, Viktor.

So my problem was actually not related to OSX but to compatibility issues between minor releases. Thanks to your replies I sorted it out. And I finally understand your versioning concept. Thank you Manuel, good job! Regards, Viktor Veličko WTools3D s.r.o. www.lwcad.com