Thanks for pointing it out, changed it 🙂

Hey,

I now know how our API will look like in this regard in 2026.0.0. Its compile/runtime behaviour will be as for 2025.2.1 and before. And we will introduce a new flag NOHANDLEFOCUS which must be set when attaching the area when one explicitly wants to ignore focus events. So, you will not have to change your code when you were happy with your user area behaviour as it is has been.

Cheers,
Ferdinand

Ok? will do

Love the mxutils and GeDialog Changes, I use these features almost every time, thank you for having a more refined official version.

Thank you to the SDK team for their work achievements

Cheers~
DunHou

Thank you

Hey,

so, I fixed this now, in the sense that the TOC is now back in these classic API type and module pages.

c2f5944c-90e4-49f9-a194-44f7be96b281-image.png

I renamed the old a bit wordily named "Functions Signatures" and "Functions Documentation" to Overview and Functions (or Methods for classes) . Opposed to the old pre 2024.3 TOCs (which were completely broken in many ways), these categories now also show up in the TOC:

adcc5c03-d5fd-4f97-b206-7d69cef2d81e-image.png
bc7bac63-8959-487a-8aa7-81e729fcc92a-image.png

The old Types and Inheritance section has been merged into root element as I do not see a good reason why it should appear in the middle of the page. The obvious thing would be to now add links to the individual elements on a page, so that you can quick-jump to a particular function. But that turned out to be not so easy with the mess we made there before and stubborn docutils. As evident by the C4DAtom example and other cases our TOC trees are very broken in this part of the docs and I now already almost spent two days with fixing things to this state.

This will be shipped in the current state with the next release of Cinema 4D. When I have some time to waste, I will try to add the function links.

⚠ The manual and maxon API TOCs are unaffected by this, they continue to work as intended. The classic API does its own thing here (as always 😄 ) which why this is such a mess.

Cheers,
Ferdinand

Hey @no1astrologer,

this will be fixed in the next release.

Thanks @ferdinand. I guess I'll have to skip on that idea 🙂 I was really hoping that there is something like .GetAllTextures or .GetAllAssets, but it seems I'm out of luck on this one.

@ferdinand you are amazing!
Thank you so much for your help, this is it. Now only remains the last step until my script to automatically recognize and replace duplicate objects with instances is complete: The UI. But that should be a quick one.

Thank you so much for your help again Ferdinand, you are a saint. Have a superb week and best wishes from Potsdam!

Thanks for the response, that's what I was afraid of.

John Terenece

Thanks @m_adam,

I had to jump through a bunch of hoops with this one, because I put the queue process into a progress dialog so that for large file arrays there's an indicator of progress. Otherwise it just appears to hang and the user won't know why. But this made it tricky when the timer is also used because of the different thread contexts involved with the timer, the progress dialog and everything else on the main thread. But with a bit of care, it seems to work.

Thanks again,

WP.