Hi, Thank you so much for your suggestion. I changed my code to iterate each surface. It works very well. Thank you for your help, which solved my problem. [image: 1623154713798-6ecf2fc3-56cc-4834-9632-0b815d3a5f39-image.png] Thanks, Manuel

Below gets the focus back on the first tab of the pyTag (after other objects have been selected), but it only works with/after a button click.. Perhaps this might be of use. def message(id, data): if id == c4d.MSG_DESCRIPTION_COMMAND: id2 = data['id'][0].id if id2 == c4d.ID_USERDATA: userDataId = data['id'][1].id if userDataId == 1: # << just a button on the pyTag with ID 1 ### do some function... # GET FOCUS BACK on the pyTags's 1st Tab: op.GetObject().SetBit(c4d.BIT_ACTIVE) op.SetBit(c4d.BIT_ACTIVE) c4d.gui.ActiveObjectManager_SetObject(c4d.ACTIVEOBJECTMODE_TAG, op.GetObject(), c4d.ACTIVEOBJECTMANAGER_SETOBJECTS_OPEN, c4d.DescID(c4d.DescLevel(1))) op.GetObject().DelBit(c4d.BIT_ACTIVE) c4d.EventAdd()

Thanks for the response, that seems to have solved the issue. John Terenece

Hi, @Boony2000 you are right, the documentation will be fixed. Cheers, Maxime.

Hello @beesperester, thank you for sharing your repository, but without further questions or postings, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @wuzelwazel, without further questions or postings, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @Chris-Chris, without further questions or postings, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @César-Vonc, without further questions or postings, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @fwilleke80, without further questions or postings, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Good to hear, thanks!

Hi! Thanks for your input! I just found the cause. There is an os.kill call on the C4DPL_ENDPROGRAM message. If you leave it out some python stuff seems to keep running and preventing Cinema from being opened again. I am assuming that's why the original author did that. I will just catch the dirty flag myself and deal with unsaved scenes before terminating the process. Unless you know a more elegant way. I will mark this as solved. Thanks again. P.S.: This is off topic, but trying to reply I would always get an error and I had to log out and in again to post this. EDIT: I found the elegant solution - Adding c4d.documents.CloseAllDocuments() before the process termination handles the save dialogs perfectly!

I already did If they didn't contact you, it strengthens my suspicion, and I can simply ignore further mails from that contact. Thanks! Cheers, Frank

Hi Maxime, Thank you! That’s a lot to take in Cheers, Frank

Hello Paula, of course, I understand these restrictions, but on the other hand it is in this case hard to just guess the problem. Feel free to reopen this subject at any time. Cheers, Ferdinand

And sorry @kbar, @C4DS, @aturtur I should have found it earlier, but after looking at how to implement it, I figured out it's already possible since R21 with the flag DR_COLORFIELD_NO_SCREENPICKER import c4d class MyDialog (c4d.gui.GeDialog): def CreateLayout(self): self.AddColorField(1000, c4d.BFH_LEFT | c4d.BFV_TOP, colorflags=c4d.DR_COLORFIELD_NO_SCREENPICKER) return True if __name__=='__main__': global dialog dialog = MyDialog() dialog.Open(c4d.DLG_TYPE_ASYNC, xpos=-2, ypos=-2) Cheers, Maxime.

It’s too bad, but thank you for your answer Manuel.

Hi @ferdinand RE: Please note that this is not a commitment of us to do this regularly . . I understand. Thanks for the detailed explanation and background theory for the answer. Have a nice ahead! Will close this thread now.

Dear community, this bug has been fixed and will be integrated with an upcoming release of Cinema 4D S24 (hopefully the next one). Cheers, Ferdinand

Hey @ferdinand Thanks again! I think the question is closed