Ok, that's a shame. Would have been useful. Thanks anyway.

Just to follow up, what Maxime suggested worked perfectly. No more cheating, basically just c4d.StopAllThreads() dialogThread.Start() dialogThread.Wait(True)

@m_adam wow! I did what you say,it works!! you are so cool!! thank you very much!!! yeah!!

Amazing! Thank you again Andreas!

Hi Andreas, Thank you very much! It works like a treat and I appreciate your thorough explanation! Happy Friday! Andre

Hi Florian, sorry, to hear about this issue. To be honest, I can hardly believe that it's those parameters or sliders causing a crash on plugin registration. I'm more thinking of some memory maybe being trashed beforehand. But in the end, it doesn't matter so much, what I do believe or not or what I might suspect, we want to assist you in solving this riddle. As we have no evidence for issues in the described area, nor are we able to reproduce it via a simply example, I'd like to ask you for some more information. Could you maybe provide us with a stack trace, when the crash happened? Either from within Visual Studio or via the crash reporter (in the latter case, please notify me here, I need to look out for the report). I have turned this thread into a question. Cheers, Andreas

That's great, Andreas. Thanks! I'll kludge on until then.

Hi Andreas, Ok, so I have to rotate the points to rotate a polygon. I thought so. That is why I assumed that when I can rotate points, I can rotate polygons. Thanks. Regards, Pim

Hi, don't be surprised, I have turned your thread into a question. The problem is, that the document will actually not be animated (or lets rather say, it will not be evaluated or executed) when calling SetTime(). Additionally you need to call ExecutePasses(). The BaseDocument manual in our C++ SDK documentation contains some extra information on this topic in the sections Time and Animate. Cheers, Andreas

@m_adam thanks for R23.110 C4DPYTHONPATH37 !

One last note. I just tried this on OSX and it works fine. So it is just an issue for Windows machines and whatever version of IE the widget is using.

@a_block No inconvenience at all, just happy to hear it's not only me!

Thanks @r_gigante that's what I thought.

@s_bach I was beginning to wonder if I was beating my head against a brick wall. Apparently so. Thanks so much for alleviating the pain! Well, I learned quite a bit about Python in the process so not really a loss. Guess I'll try moving on directly to the C++ version.

Hi, I'm glad this already got solved. I just wanted to mention, I have added code tags to the initial post. Cheers, Andreas

Hello and welcome, what exactly do you mean with "export keyframe data"? Do you want to write data into a file? The best way to develop such code would be in a Python script that you can edit and execute in the Script Manager. A XPresso Python node is meant to contain code that is executed as part of XPresso to define the behavior of the XPresso network. A XPresso Python node should not be used to modify the scene or to perform I/O operations. A CTrack object stores the DescID of the associated parameter. You can access that DescID with GetDescriptionID(). Alternatively you can use BaseList2D.FindCTrack() to search for the CTrack associated with a certain parameter DescID. You find an example on GitHub. You find general information on how to use CTrack and DescID also in the C++ documentation: CTrack Manual DescID Manual best wishes, Sebastian

@a_block Thanks for the update. Much appreciated!

Hi Mike, please check this thread to properly use the Q&A functionality. Cheers, Riccardo

@m_adam thanks so much for all your help on this!

Hi, as I said in my previous post, I have no ideal solution for you. By "awkward" I wanted to express, that I expected this to be not the solution you want, after all such a move by resizing would imply at least to size operations by the user, if both screen are equal size. And unfortunately I have nothing else to offer. Sorry. Bye, Andreas