Hmmmm, well, on the one hand this function is a nice thing: It really does do the escaping for me, so the spaces in the URL are correctly replaced with "%20".

But it does not handle anchors in a URL.

This URL works fine:
file:///Applications/Maxon/Cinema 4D R22/plugins/myplugin/help/content/omyobject/omyobject.html

But this URL is not opened, instead an error (code -43) is thrown:
file:///Applications/Maxon/Cinema 4D R22/plugins/myplugin/help/content/omyobject/omyobject.html#MYOBJECT_ATTRIBUTE

That is a pity.

The distinction between pixel color and contribution of the ray to the pixel really helps clear things up. Thanks for all the help 🙂

@m_magalhaes said in What's the state of Ngons in Python?:

About the bugs on the forum, we have introduce few month ago new tags "Bug report" and "Bug Fixed". We are also adding some tag in our bug database to retrieve faster the post on the forum. I know it's not perfect and sometimes we may forgot to add this tag on the first post of the thread. But it's better than nothing.

Yeah, I'll try to use that in the future although it probably won't affect existing threads (a lot of valuable knowledge still resides in the "old forum" parts).

@Cairyn said in What's the state of Ngons in Python?:

Anyway, I don't think this issue is of huge interest as you said there's a replacement in the new kernel already, which will probably come with a diferent tesselation algorithm, so I present it here as a curiosity.

Don't get me wrong, all modeling command have been migrated to the new modeling kernel. If you are using SendModelingCommand, it will use the new kernel.
So what you see now in S22 and R23 (ok you will see in R23) IS the new kernel. There will be no better tesselation.
I consider this as a bug.

As a Perpetual user, I'm still on R21 (as tagged) so is this also the new kernel? AFAIK the new kernel has been working behind the API for a while now, being gradually introduced into the functionality, so it's possible that this bug still persists.

I can't test it on a demo of S22 for you, as the current licensing does not allow me to install one.

The new modeling kernel isn't exposed yet. But it is used. I understand, it's a bit confusing. We are moving Cinema4D to the new core. But as long as some part of Cinema4D are using the old system (object manager for exemple), the new core need to "translate" that to the classic API. (...)
I hope it's clear.

Sure, I have a few decades of programming under the belt. It's just a bit difficult as non-Maxon developer to see the details. Seeing only the API (and therefore the user-side of the translation layer), I can't always tell what the underlying data model really is; what's stored as attribute, what's calculated on the fly, what's internally cached for fast access, what's abstracted and what's plainly stored... I may make wrong assumptions on the internal workings.

this look like a valid ngon but i will ask 🙂

It probably is valid - I don't see a reason why it should be forbidden. I just notice that the tesselation algorithm tends to avoid such "inner polygons". That may not be intentional (based on a rule) though, but just a consequence of how the algorithm works.

Thanks again,
-- Cairyn --

yupyup, BaseSelect has no connection to the original object it actually selects from, not even in the cases where you get a pointer to the BaseSelect returned and change the selection directly through it.

That's why we need the max parameter for SelectAll and ToggleAll -- the BaseSelect doesn't know what "all" even is. (Not GetLastElement()!) For GetRange() though, that reasoning does not apply.

Now let's see whether I can crash C4D with inconsistent edge selections...

Thanks zipit and Maxime,

I use the MSG_BASECONTAINER solution now,
thanks for the example !

one question here:
you always return True from the message() function
is that necessary?

the docs here
https://developers.maxon.net/docs/py/2023_2/manuals/introduction/python_tag.html?highlight=python plugin
just says :
Return type: bool
Returns: Depends on the message type.

...

and a bit off topic :
is there a message, when a python tag or generator gets enabled / disabled by the (generator) switch in the object manager?
can i catch that?

Thank you @m_adam 🍻

This is still missing in the Python SDK .....
☹

@kbar said in Decoupling source from SDK project:

Since Maxon also updates the ProjectTool when a new version of C4D comes out and it may have new flags or optimazations and changes to the project structure for XCode and Visual Studio.

From what I can tell it's pretty stable, also I don't mind what someone else thinks my compiler optimisation flags should be.

Maintaining your own CMake version going forward for R20, R21, S22, RXX etc... would be a massive pain and just slow you down.

Not as painful as you think it might be, also not as slow.
Whatever floats your boat. 🙂

@gheyret great to hear! Looking forward to seeing what it is you are creating.

Thank you so much, this works like a charm!!!

@m_magalhaes Thanks, Manuel! 👍

Oh wait, I think I found a way. In case anybody else wants to know, here it is...

In the PrefsDialogObject:

Bool MyPrefsDialog::SetDParameter(GeListNode *node, const DescID &id,const GeData &t_data,DESCFLAGS_SET &flags) { BaseContainer* bc = MyPlugin::GetPreferences(); if (!bc) SUPER::SetDParameter(node, id, t_data, flags); switch (id[0].id) { // If PREFS_MYPLUGIN_SOMEVALUE was changed, store value and notify plugin objects in all open documents. case PREFS_MYPLUGIN_SOMEVALUE: bc->SetInt32(PREFS_MYPLUGIN_SOMEVALUE, t_data.GetInt32()); flags |= DESCFLAGS_SET::PARAM_SET; // Iterate open documents for (BaseDocument *doc = GetFirstDocument(); doc; doc = doc->GetNext()) { // Send broadcast message to each document, use unique ID doc->MultiMessage(MULTIMSG_ROUTE::BROADCAST, MyPlugin::UNIQUE_ID_PREFS, nullptr); } GeUpdateUI(); return true; } return SUPER::SetDParameter(node, id, t_data, flags); }

And then, in the plugin object:

Bool MyPluginObject::Message(GeListNode *node, Int32 type, void *data) { if (type == MyPlugin::UNIQUE_ID_PREFS) { GePrint("Aha! My prefs have changed!"_s); return true; } return SUPER::Message(node, type, data); }

I guess VirtualBox is just not a good choice then. Damn. But thanks for the answer!

Cheers,
Frank

@android Here's a thread for reference regarding the limitation of a Generator spline:
https://developers.maxon.net/forum/topic/12596/is-it-possible-to-get-a-spline-wrap-object-to-use-a-python-generated-spline

@m_magalhaes

Thanks! It works as expected.
So that's what you mean by UniformToNatural. Basically, even if the segment guides are not the same as spline points, it will conform to its overall shape.

hi,

Group is the key in UI. Simply add a SCALE_H; property for your slider. so for that two columns group, the slider will take all the place minus the button.

GROUP { COLUMNS 2; REAL ONEFLOAT { CUSTOMGUI REALSLIDER; SCALE_H;} BITMAPBUTTON BUTTON_ID { SIZE 16; TOGGLE; BUTTON; ICONID1 5160; ICONID2 5159; } }

Cheers,
Manuel

Hi,

jeah, that is probably somewhat the reason. Although Python has true statically typed arrays, which also can be used to directly in-place manipulate C arrays (i.e. array.array), from what I understand it is quite cumbersome to achieve such linkage. This is probably the reason why Maxon does not bother in this case and others like for example vertex colors. Including these access points is still a bit puzzling though. Maybe they are somehow used internally? But I cannot think of a case where this would make sense.

Cheers,
zipit

hi,

everything have been said, nothing to add here 🙂

Cheers,
Manuel

@ivodow said in Thinking Particles allocation failure in new document:

So, would ExecutePasses() with the BUILDFLAGS_EXPORT flag set be typically called just before exporting to alembic (to be on the safe side)?

the exporter is calling ExecutePasses several times, you don't really need it.
And because the scene can be sometimes quiet complexe, you have to call it several times in a row.

for example, in the alembic exporter :

68d39647-ef56-430b-ae1a-2189e1b83617-image.png

Cheers,
Manuel