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

@ferdinand said in VariableChanged Struct is missing its maps?:

TEST TEST forbidden to post?

No, it's not

Sorry, that's the message from the system that I got in the other thread, repeatedly. So I tried it here, and it posted without difficulty. Then I tried in the other thread again, and it worked. Then I deleted all these postings. But as the original message that I tried to post was lost to the error, I didn't bother to write it again.

Quite strange error, haven't seen it before, and it didn't come with any explanation WHY it was forbidden to post.

Hi,

Sorry about not having time to investigate the gradient part of your question. I was waiting for feedback about the color presets.
With the new asset browser out there's no point into investigate this question furthermore.

Cheers,
Manuel

Hi,

sorry but, we don't have enough ressources to investigate why it have been coded that way 14 years ago and what could be the side effect on changing it.

Cheers,
Manuel