Hey @datamilch,

@datamilch said in updated forum search:

Actually I was not able to respond in the Announcement forum. I just looked again and there is no reply button for me.

Good that you point that out, that was not intentional. The recent forum update might have changed the privileges. I have again given registered users the ability to reply to topics in this forum. Creating new topics in this forum is still restricted to moderators.

Regarding the search mode, I fully understand the different behaviors. Just had the urge to give this feedback, so i can move on.
I really appreciate your 'hacky' solution with the dark-mode, thank you! 😸

Yeah, I understand and truly appreciate that. I was just trying to explain that what might seem as 'absolutely correct' from one user's perspective, might be the opposite from another.

just a thought for consistency: since the condensed feature seems to be skin related, couldn't there be 4 skins - light condensed and uncondensed and dark condensed and uncondensed ... but since i don't know, how you did it, maybe this might become to cluttered in your backend.

NodeBB has skins and themes (two different things). The theme our forum is based on, which is effectively a NodeBB plugin, has its own setting which is also called skin (because everything else would be too easy, right 😄 ). That skin has nothing to do with the NodeBB notion of a skin and its elements cannot be extended (without messing with the source) as far as I know. That custom skin is what users see as default and dark skin.

The easiest solution would be to inject some custom JS which listens for search result page events and then injects one or multiple toggle buttons and their associated logic into that page. The result will be then that one can toggle the folded state of all results on a page with one click (more or less what is currently already possible in the search options). But one would have to do this single click on each result page. Anything which is more persistent than that is too much work.

Cheers,
Ferdinand

@JACK0319 Great work !

I have been using ualib for some plugins and worked very well for whatever a beginner or experienced programmer , It's definitely worth trying it 👍

0cf6ade8-8bae-4cd8-96f0-ff3f143c1306-image.png

Hello @render_exe,

Thank you for reaching out to us. Unfortunately, as already pointed out by @Dunhou, questions about third party APIs are out of scope of support:

Forum Guidelines: Scope of Support

We cannot provide support on learning either C++, Python or one of its popular third party libraries.

Thank you @Dunhou for providing such a nice community answer. Since this topic is not about the Cinema 4D SDK, I have moved it to General Talk.

Cheers,
Ferdinand

Entschuldigung. Vielen Dank.

Thanks, @ferdinand

Yes seems intended but could be troublesome if you use mograph / redshift object color to drive something ?

C4D Version : 2023.1.2

A solution to guide the user could be to disable the object color when set to "Render Instance" , but from a UX standpoint I am not a fan of taking away control from the user.

thanks for taking it to CS
kind regards mogh

Hi I can confirm that from nodebb side there is still no way to do it.

Rest assured that we are also annoyed by that so as soon as this is available we will enable it 🙂

Cheers,
Maxime.

Hello @conductor,

thank you for reaching out to us. You can certainly post a job posting here, but it should happen in the General Talk forum. It can contain everything which is not directly related to one of our APIs but loosely related to CGI or development.

The same applies to this thread of yours, I have moved it to 'General Talk' .

Cheers,
Ferdinand

Thank you @ferdinand !

Hey @kantronin,

Thank you for reaching out to us. I would recommend having a look at the Modeling Python Examples. They are a bit hidden, but in the Geometry section I went over the general classic API geometry model of Cinema 4D.

Regarding your core questions:

Removing points from a polygon: Without wanting to be overly pedantic, I must point out that polygons only index vertices, they do not hold them; CPolygon references with its fields a, b, c, and d the vertices of the PolygonObject it is attached to. In this sense removing points from a polygon is not possible, you can just de-index them. Cinema 4D expresses both triangles and quadrangles with the type CPolygon, i.e., as quadrangles. A triangle simply repeats its c index in its d index. I explained this in the modelling examples in more detail. Removing vertices or polygons from a PolygonObject: There is neither a PolygonObject.RemovePolygon nor aPointObject.RemovePoint if that is what you are looking for. When you want to change the vertex or polygon count of a PolygonObject, you must call PolygonObject.ResizeObject and then call PointObject.SetAllPoints() and for each (new) polygon PolygonObject.SetPolygon. The operation_extrude_polygons_s26 example covers this subject, although I go there into the opposite direction, I increase the point and polygon count rather than decreasing it.

PS: Useful might also be geometry_polygonobject_s26 because I explained there the type from scratch.

Cheers,
Ferdinand

Btw if you install the Cinema 4D Vs Code extension, pyp extension should be added as Python.

Hi @FSS first of all happy new year ! 🙂

And I'm glad that you found a solution however even if this is in the documentation we don't explicitly support PyCharm and only provide a dummy package to have autocompletion working with any Python instance. But C4dpy is not supported by all IDE and we can't provide any support there.

If you want to have a better IDE workflow we released a plugin for Visual Studio Code, requiring a Cinema 4D plugin and a VS Code plugin.

Finally I moved this topic to general talk as it this is nothing related to Cinema 4D API.

Cheers,
Maxime.

@ferdinand

Thanks for the pointers.
I'll try to look up those options.

Will close this thread now.

Hi @InterfaceGuy, this forum is only about Cinema 4D Scripting and plugins, please reach the user support via the maxon website.

Cheers,
Maxime.

I see.
Thank you for the reply Manuel 🙂

Hey @kng_ito,

So the normal direction of the generated polygons was the point!

It depends a bit on what you mean by normal direction, but generally speaking, normals only play a minor role here.

Wenn all segments would always lie nicely inside a plane, it would be easy. Just compute the mean point for each segment and then come up with some cockamamie rule when you would consider two segments not being in a shell-hole relation (as I did above with 'a hole is not a hole anymore when T farther away from S than S is tall or wide').

In practice things do not always lie nicely in a plane. So, you then must first project them there, find their mean plane. So, the 'point' would be finding the mean plane / dimensionality reduction. I cooked up an small example below.

Cheers,
Ferdinand

Result (the plane gizmos are a bit buggy and sliding, did not debug this. But that is why I turn them off):

The file:
spline_hole.c4d

@m_adam

Thanks for the response. Modifying the environment varialbles works for my use case.
Closing the thread now.

@m_adam

Thanks for the confirmation. Will close the thread for now.