Hi @blastframe, yes, that would be one, and probably the more modern way to do it. I personally like also an explicit call to the base implementation. I think it is more readable for someone else reading your code. But that is probably a rather subjective choice. So for clarity, I am speaking about something like this: foo = bar * baz return c4d.gui.GeUserArea.InputEvent(self, msg) There is of course the advantage of super taking care of calling the proper implementation(s) for you which is not taken care of by this approach, but you cannot have everything and in this case things are rather unambiguous for us here ;) Cheers, Ferdinand

@mp5gosu Sorry, I missed it! That works! In case other devs have a solution, I'll mark yours as the right answer. Thank you!

@ferdinand Thank you, Ferdinand for the thorough answer and ideas for workarounds. I don't quite have my head around how to use threading in Cinema 4D yet but you've inspired me to look into it. Thank you!

Hi @blastframe, so this is a bug that happens independently of Python. It also not connected to your example using a dangling dialog, but to the fact that it is using a dialog. When you implement some form of NodeData plugin and a FONT resource element in it, this bug won't happen. I have opened a bug report for this. For now you would have to either use my little workaround or move outside of a GeDialog environment an implement the whole plugin as some form of NodeData plugin. If a dialog is of high priority for you, you could also display an instance of that node in a DescriptionCustomGui inside your dialog. Which should work and somewhat be a mix of both options. Cheers, Ferdinand

@ferdinand You are an absolute genius. Thank you so so much, Ferdinand. Incredible!!

Thank you for letting me know, @ferdinand !

@ferdinand That's very helpful, thank you!

@ferdinand you were clear and example is pretty good, I got the idea. No need to write code for me ;) But it's not trivial overall, I just need to spend some time on this. Thanks again.

hi, thanks @mp5gosu for the answer. About inserting material before making some changes, there's no real right way of doing it. It just that if something go wrong about the change you are doing, you have to remove the material from the document, while if you don't insert it, you don't have to. As @mp5gosu said it's better to insert the object in the document before linking them. Even if should work if you insert the material after. Cheers, Manuel

hi @Boony2000 , these are Visual Studio Intellisense errors which you can safely ignore. If they bother you switch the filter from "Build + Intellisense" to "Build". Cheers, R

@blastframe said in Updating F-Curves in Timeline on EditSlider Drag: What's c4d.EVMSG_FCURVECHANGE for then? After a quick check (sorry, I should have checked yesterday for a more complete answer) literally nothing. It's used nowhere. Cheers, Manuel

@ferdinand Thank you for this; it makes things much clearer. I am very grateful we have the forum to clarify these issues.

@ferdinand That was exactly what I was seeking, thank you, Ferdinand!

hi, this shouldn't make any difference, what do you mean by "my own FIELDLIST gui element" . Can i see how do you add it and initialise it ? Cheers, Manuel

@zipit Thank you very much, Ferdinand. This helped me a lot!

@zipit Thank you for the information.

All right, thank you for all the help. I'll close this now.

Glad you found a way and yes I think it's safe now :) I guess there is no more open pint? If so I let you define your topic as solved (see Forum Structure and Features - Ask as Question If you don't know how to do it). Just in case a BaseContainer can also store a BaseContainer. so you could store your own BaseContainer at the ID_PLUGIN And in this BaseContainer at ID 0 stores, the obj counts, and then you can safely iterate over it. Cheers, Maxime.

@m_adam Thanks for the clarification. Regards, Georgi.

@zipit Hi, thank you for the message. Yes, I believe I already understood everything you explained and I do appreciate your efforts. I knew I wasn't doing anything with the descid in my code, I was just confused as to why when I change one attribute, I was getting MSG_DESCRIPTION_POSTSETPARAMETER messages from all of the attributes as opposed to just the one attribute. Perhaps it is something else in my code that is sending those. Regardless, it isn't hugely important, I was trying to be as efficient as possible. Thank you.