hi, your question is sometimes not obvious Even with the scene it's a bit compicated. What i can say about your code is that you should be more defensive in your code. Always check the value before continue. For example what if the object is not found ? You should continue to the next item or stop ? for item in spline_UD: rs_mat = doc.SearchObject ("S" + str (item) + " Gas") if rs_mat is None: # Because we don't have object to continue, we iterate to the next item. continue ... Cheers, Manuel

Hello, thanks for the answer by the way you could also clone the renderdata, modify the clone and send it to as a parameter to the function RenderDocument. That way, you don't have to "restore" them. Just in case, don't forget that data may not be saved in the BaseContainer. Cheers, Manuel

@zipit Thanks for the confirmation!

@m_adam said in PolygonObject.SetSelectEdges() and the Neighbor() class, a giant dilemma: ... Hope it answers your questions, Cheers, Maxime Thank you Maxime, this is a lot of useful info. Let me think through all of this and reply here if I have any further issues.

@m_adam said in First Time calling SetAction does show the Brush tool's AM: And I did test only on R21 so be sure to check again because I wasn't able to reproduce as you said with default layout in R21. Cheers, Maxime. I am using R21.207 and with default layout see the brush tool in the AM (identical to what happens with R20.059). For safety, I have now tested your solution on R21 and works as expected.

@m_magalhaes No hurry, for now there's just one place where I need this, I get it using the BaseContainer. But I will probably use it more often, so if the DOTS example is updated I can replicate the solution to my own type and remove this workaround. Thanks!

hi, back to the subject, i was tracking the bug and I discovered it was on my chair. After messing around too much about the code, I was doing something very wrong. when you register your scenehook what is the level ? (last parameter of RegisterSceneHookPlugin) Cheers, Manuel

Hi @m_adam . Apologies for bringing up the thread again. I just have a follow up question. The def Message works well for the consecutive duration of the dialog. But for the initial life (i.e on startup), the def Message will not be executed . Is there a way to determine the width and height of the dialog upon its startup?

@PluginStudent Thanks for the explanation. Your solution works as expected

@bentraje I don't have that much to add on your topic since I think @zipit already explained everything nicely. In any case some good resource for you about how global variable works in Python Global keyword in Python and Mutable vs Immutable Objects in Python. Regarding your last question, I think you should open a new topic, but the short answer there is no way to pass directly a variable with a MessageData, the best way is to use a scope accessible by both part and store this variable in this shared scope (can be global or any other). Cheers, Maxime.

Hi @daniell welcome on the plugincafe forum, Don't worry since it's your first post, I've set up it correctly but please for the next one, make sure to read and apply the next rules: Q&A New Functionality. How to Post Questions especially tagging. Finally, regarding your issue, you may find relevant the NodeData::GetDParameter() Manual and NodeData::SetDParameter() Manual. Cheers, Maxime.

@r_gigante Thanks for the reference. For anyone trying to achieve the same, here is a sample file. https://www.dropbox.com/sh/z1lzyphp8qnt9kw/AAB2P5gNo16IHafgc6xPEsy4a?dl=0 Thanks again for @zipit for the help.

@zipit work fine thanks a lot

@m_adam Thanks! Works as expected

Thanks @PluginStudent

Got it. Thanks, again, zipit for you answer.

@r_gigante Thanks for your reply! You were absolutely right about checking input type. When i did a simple type check everything started to work as it should!

Cool! Thanks.

Hi, thanks, that answers all my questions. Cheers, zipit

I'm sorry for the huge delay asked for this question, but it appears, that this dialog layout is hardcoded in the default Cinema 4D layout, so when you open it this dialog, it loads this layout by default since it's saved in the default Cinema 4D layout. Unfortunately, there is no way to do the same thing with code but you can split your GUI in 2 parts and let the user build its own layout with all the Command and your Dialog bellow. Cheers, Maxime.