Any update?

Just to point out, I already answered & posted a full sample scene in this thread: https://www.c4dcafe.com/ipb/forums/topic/109504-python-vertex-map/ plus a detailed explanation on how vertex map calculation works in a free post on my Patreon: https://www.patreon.com/posts/script-club-1-07-34384586 (Just so we don't get work duplicated.)

Hi @heilei thanks again for the comment! We'll try, where meaningful, to improve the typography in future releases. Best, R

Ok, got it. Thank you for your reply and clear explanation, r_gigante, much appreciated!

OK, thanks a lot for the quick answer! Cheers

Hi; if you're looking for Python development - I'd have some time on my hands. Long-time C4D user and developer (currently creating a Python-for-C4D course actually). Not in the UK though (mainland Europe). If you want to talk about some details, drop me a mail under cairyn (at) tigress (dot) com.

Once again, thank you, Manuel. I had to do a few changes and it is working now. I even made it select the faces that are within a certain angle from the camera. Here is my code: for i,poly in enumerate(faces): a,b,c,d = poly.a,poly.b,poly.c,poly.d pta = points[a]*mg ptb = points[b]*mg ptc = points[c]*mg ptd = points[d]*mg v1 = pta-ptb v2 = ptb-ptc normal = v1.Cross(v2) normal.Normalize() if c != d: center = c4d.Vector((pta.x+ptb.x+ptc.x+ptd.x)/4.0,(pta.y+ptb.y+ptc.y+ptd.y)/4.0,(pta.z+ptb.z+ptc.z+ptd.z)/4.0) else: center = c4d.Vector((pta.x+ptb.x+ptc.x)/3.0,(pta.y+ptb.y+ptc.y)/3.0,(pta.z+ptb.z+ptc.z)/3.0) direction = cam_off - center norm_dir = direction.GetNormalized() angle = NINETY - normal.Dot(norm_dir) if (angle > 0.0 and angle < max_ang): selection.Select(i)

Hi @wuzelwazel, thanks a lot for sharing your progresses on the Ptex Shader and for sharing your code. I've moved the thread to the more appropriate "General Programming & Plugin Discussions" hoping other developers could contribute to the discussion. Cheers, Riccardo

https://developers.maxon.net/forum/topic/11570/plugin-affecting-c4d-modules-startup/9

@Cairyn Hi, Thank you. Solution: Float GeIncircle(Int32 n, Float r) { return r * cos(PI / n); } Float max_rrad = GeIncircle(n, r);

@r_gigante Hi Riccardo, thank you for your detailed response. That allowed me to find the exact formula. l / (2 * tan((180 / n) * 3.14159 / 180)) Regards, Mustapha

Gotcha. Thanks for the code and confirmation. For my code, it's not really a simple printing the ID. Each ID corresponds with a separate function/script. I guess I'll just store them in a separate list. Separate ID list and separate function script list. Then execute them by matching index.

Thanks for the response @mp5gosu Yea, this "another level of abstraction" might bite me in other sections of the code but this is the only way I can be sane for now. hehe @m_adam RE: it's also advised to use only iD superior to 1000. Thanks for the note. RE:here is one of the few possible ways The code works as expected. Thanks again! Should make things easier now

@m_magalhaes Thanks for your reply

@s_bach said in Communication between DescriptionTool and GeUserArea: The typical modern approaches are patterns like Model-View-Controller or Model-View-Presenter. In such models, you don't "send data around". Thanks for mentioning this. As stated in my opening post, this is what I have been using, where the "model" is a singleton class, available as a global variable to all plugins to synchronize and share data. Maybe not quite the exact wording. I was just wondering if there is another means of providing this "model" instead of using an instanced (singleton) class via a global variable? So in your example, the interaction with the DescriptionToolData would write data into the model. And the GeUserArea would read that data from the model. The example I provided isn't making use of a "model" as it already represented too much code just to point out the bug that slipped into R21. There I indeed used a very simplified solution by "sending data around". But an overall "thank you" for bringing up the model-view discussion, as this made me realize I could use an observer pattern in another project of mine which would fix its current poorly chosen design. Daniel

Hi Ashton, thanks for sharing your code. Best wishes for the incoming new year! Riccardo

Hi P_ron81 thanks for reaching out us. Considering the very early release of Cinema 4D you're referring to, I'm sorry to say we don't support it anymore. I can't also confirm or deny, without having a look at the original code from CactusDan, about the feasibility to build it against the APIs shipped with R13. Cheers, R

[image: 1576839159860-maxon_x-mas_late_shift_low.jpeg] Dear Developers,     we can't be any happier to receive your holiday season greetings and to know that you feel like at home here. We've faced a few changes across the last years and we've tried to manage them limiting side effects to our support capabilities and effectiveness. In our Team we embrace changes for the better, thinking to the opportunities they might generate rather than to the certainties that they blow away and we'll stand for it all the way long. We also appreciate, and we are greateful for, the level of contribution that we perceive from You, without which, our community, wouldn't ever been the same. Best wishes to you and your loved ones looking forward some relax during the Xmas time and an enthusiastic 2020. Sincerely, Your SDK Team