Hi @delizade, Thanks @a_block for helping out! @delizade you can find the description for the priority options in the Python Tag section of the user manual. Cheers, Ferdinand

hi, i was saying not to use the same ID (in case of conflict) But it seems that there's no conflict neither with the symbol name or the symbol ID. A bit strange. Cheers, Manuel

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

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

@m_magalhaes Now i know how to solve my problem! Thank you for your reply. Cheers！

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

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

@zipit I just read this（Connect C4D with Tkinter） post，It does seem to help me Thank you again！

Hi @lasselauch, we talked about your problem this morning. There are two ways of looking at your question: You are interested in the event of a closing document (i.e. present progressive) and you want to react to that event by making some changes before this process is finalized (i.e. the document closed). As already stated yesterday by me, there is currently no way to do that in a GeDialog. You will need some kind of node for that. It is also noteworthy that currently CommandData is bugged in this regard in Python. As @mp5gosu already pointed out, MessageData is a really good way to go, unless you do not have already something like TagData plugin where you could squeeze in that functionality. You are interested in the state of the loaded documents list, i.e. if a document has closed (past tense), but not exactly when it happens. This is possible in a dialog. You already provided your own answer here (thanks for making it visible to everyone). The basic idea is just to build some hashmap/list to compare against what Cinema considers to be loaded documents. As an added note, you might want to look at GeDialog.Timer, which will let you execute things in fixed intervals, in order to get closer to the point of when something happened. This won't be to much of a performance strain if implemented carefully. Cheers, Ferdinand

Hi, I understand that this thread has not yet come to a final conclusion, but without further feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

Thank you @m_magalhaes !

Hi @pyr, thank you for reaching out to us. I am afraid we will need a little bit more than that, as otherwise it will be very hard to answer your question What kind of plugin do you implement? What does it do or what would you consider as running? On a very abstract level you cannot really prevent plugins from running other than not registering them at the start of the application. But you can of course modify their output depending on basically everything, including render events and at what time offset some given document is. Cheers, Ferdinand

@zipit Thanks, I thought so... but you never know whether some functionality has a hidden internal purpose. Deprecating it will probably be the best solution.

@Cairyn Thank you for your reply. The "odd result" it's means the scene is empty , no objects were generated. According to your explanation, I have solved the problem. And it's just an exercise code. Thank you again !

Hi @jenandesign, thank you for sharing your little setup. I think your suggestion is great, but the problem is: We cannot handle feature requests in the SDK-team which are not directly concerned with one of the APIs. And although Cinema's old node editor is kind of "coding-related", it is in the end not directly related to one of Cinema's SDKs, which is the ground we do cover here. So I would have to ask you kindly to bring up your suggestion with Maxon's end user support, as they do handle these kind of requests. Cheers and thank you for your understanding, Ferdinand

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

@zipit @lasselauch thank you both for your time and knowledge!

Python plugins do not work reliably in R23 on OSX 10.13.6. The C4D minimum spec is for 10.14.6 as Riccardo mentioned. And even if you try to debug a plugin on 10.13.6 what you will notice is that many calls (such as print) don't even work on this OS. So you can't even write anything out to the console to see what the problem might be. No amount of re-installing C4D will help you at all. You just have to let your customers know that the minimum spec for R23 is 10.14.6 and not guarantee any support for anything below that spec.

Thanks for the confirmation. (Follow-up questions moved to a separate post)