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 @PATPAT, you can do it, you just cannot use the dummy package for it, but have to use the c4dpy interpreter instead. Cheers, Ferdinand

@ivodow how is your ConsolePrint() different to a simple print() statement? in my test i didn''t get a real time output with ConsolePrint() best, index

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

@WickedP yes you can assume it. Cinema 4D first loads all dlls, then PluginMessage is forwarded to each dlls.

Thank you for the explanation @ferdinand. The example makes sense even for a beginner like me, that's great

Hi @Filip, okay, thank you for the clarification. Cheers, Ferdinand

Wow, I never thought of that. Very good to know, thank you for asking! Cheers & have a nice weekend, Frank

Thanks, seems to be working now, thanks.

Hi @Sturdy_Penguin , without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Hi @kosmos3d, without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Hi @SolarPH, without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Hi @C4DS, with some delay comes here a request for closing this. If you want to keep it open for now, you can push it one more cycle ahead, but at some point I will insist on closing it without further activity. Thank you for your your understanding. Without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Hi @jochemdk, without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Hi @mastergog, thank you for reaching out to us. I can reproduce your problem and this would have not been something which we would have expected. If you go significantly over one million segments (1.1 million still works for me for example) no matter if in one node or scattered over multiple nodes, the viewport will freeze. It is a bit hard to assess for us at the moment if this a bug or just a limitation of our viewport API. We will investigate the problem and I will report back here if there are going to be any short or mid-term fixes for that (or not if this is a limitation). For now there is unfortunately nothing you can do, since spreading out the segments over multiple nodes won't help you. Sorry for the inconvenience and cheers, Ferdinand

Hi @ferdinand, Thanks for looking into this. It is not so crucial to hide the handles - I will try the custom GUI approach as you suggest.

@m_adam Thank you, Maxime! Have a good weekend.