Nice, congrats ☺

I have to admit, I forgot to turn this thread into a question. I did so now and I also marked it as solved, as your last post seems to imply.

Cheers,
Andreas

Hi Andreas,

Thank you very much! ☺
It works like a treat and I appreciate your thorough explanation!

Happy Friday!

Andre

That's great, Andreas. Thanks! I'll kludge on until then.

Thanks to both of you.

I originally thought solution 2 would be the way to go, and have proceeded in that direction ... but the more I look at the result the more I am getting convinced that this wasn't the right approach to deal with the issue.
So, I am still open for solution 1. But will try yet another solution, inspired by the reply from WickedP.

I intentionally didn't include a solution where I would create iCustomGui / GeUserArea for each separate gadget. As I thought this would result in drag and drop to only work when hovered over the separate gadgets, and failing when mouse would hover over the space between these gadgets.
But using a global drag and drop function on the dialog itself (instead of all separate gadgets) will actually provide for a complete solution.

EDIT:
Set the state of this post to "Solved".
In the end I went for a complete different solution. Not using any GeUserArea at all. As such, I could simply position and use EditText the way it was intended.

Hi Steve,

having the USE_MAXON_API being defined - actually using C4D=true in projectdefinition.txt - is required in order to be sure that all the cinema.framework classes are properly compiled. Although there could be situations where some cinema.framework classes can work without that define, we highly discourage this approach since you can end up in situations where the code compiles until you include that specific class which indeed needs that define (which it's already happening in that case).

If specifying C4D=true actually brings too much pain, please open a new thread and let's proactively discuss the issues your code is facing and let's get rid of them.

Best, Riccardo

Hi Florian,

sorry, to hear about this issue. To be honest, I can hardly believe that it's those parameters or sliders causing a crash on plugin registration. I'm more thinking of some memory maybe being trashed beforehand. But in the end, it doesn't matter so much, what I do believe or not or what I might suspect, we want to assist you in solving this riddle.

As we have no evidence for issues in the described area, nor are we able to reproduce it via a simply example, I'd like to ask you for some more information. Could you maybe provide us with a stack trace, when the crash happened? Either from within Visual Studio or via the crash reporter (in the latter case, please notify me here, I need to look out for the report).

I have turned this thread into a question.

Cheers,
Andreas

Hi Frank,

actually I think, all the examples on GLProgramFactory have been there for quite I while. I just checked and they were already available in Cinema 4D R13, maybe even earlier (there are actually quite a few, see GitHub).

Unfortunately that is all we have on this topic, chances are pretty bad, we can shed any additional light on this topic.

I turned this thread into a question.

Cheers,
Andreas

@m_adam Wow, this is truly great. What a fantastically written response, I really appreciate it! Learning a bunch from this example, way more than I asked for. 😄

Thanks again

Jenny

P.S. if only the py4d documentation had examples like this, we would all be better programmers 😋

Thank you for the kind help!

@m_adam: The plug-in you have linked is very useful. I could fix some problems with the "Select polygons by normal direction" function.

Working with badly constructed meshes is no fun job either way.

Kind regards,
Julien.

Hi @Jvos,

First of all, (no worry at all) I would like to remind you to read How to Post Questions especially the part about categories.
Since your topic is related to Cinema 4D please next time create a topic within cinema 4d development. (I've moved it).

Regarding your issue, pretty much all parameters in Cinema 4D are stored in a BaseContainer.
A BaseContainer is a dictionary which links an ID (Int) to a Data.
When you are doing Object[Something] you access the value within this BaseContainer.

If you write in the console c4d.REDSHIFT_LIGHT_PHYSICAL_INTENSITY, it will print you the ID of this parameter.
Then to get the value of a parameter which is stored in the object's BaseContainer, you don't have to pass a string, but the ID, which is registered with a SYMBOL NAME because it's easier to remember than an arbitrary number (In some case there is no SYMBOL equivalent for an ID).

So as @mikeudin suggested the eval function is the right way to go, or you can directly store the ID in your list.

attributes = [c4d.REDSHIFT_LIGHT_PHYSICAL_INTENSITY, c4d.REDSHIFT_LIGHT_PHYSICAL_EXPOSURE]

Finally, there is no official C4D slack/discord or chat.
Cheers,
Maxime.

Hi Andreas,

Ok, so I have to rotate the points to rotate a polygon.
I thought so. That is why I assumed that when I can rotate points, I can rotate polygons.
Thanks.

Regards, Pim

Hi,

@Jvos it looks like your question got answered. Afterwards you deleted this thread. I'd like to ask you not to do so. This forum is all about sharing knowledge. There are no stupid questions and nothing to be ashamed about. Every answered question might help a future developer.

I have moved this thread into the Cinema 4D Development category.

Cheers,
Andreas

Hi,

I'm sorry for getting back so late.
My examples should be easily adapted to random values. Our Python SDK does not directly provide means for random numbers, but Python's random module should do the trick just fine.

Cheers,
Andreas

Hi,

don't be surprised, I have turned your thread into a question.

The problem is, that the document will actually not be animated (or lets rather say, it will not be evaluated or executed) when calling SetTime(). Additionally you need to call ExecutePasses().
The BaseDocument manual in our C++ SDK documentation contains some extra information on this topic in the sections Time and Animate.

Cheers,
Andreas

Hi Ricardo,

I can't do that, unfortunately. There are several reasons why I cannot update my machine to a later OSX version than El Capitan, at the moment. I did not encounter any problems so far that could be tracked down to the XCode version.

Btw, I solved the problem. For some reason, after running the Project Tool again in a fuzzy "F*** it, it has has to work!" moment, things started working. I am stumped, as I don't know the reason, but anyway, the problem's gone.

Cheers,
Frank

Hi Roger,

with respect to the Scale tool, yes, it is impossible to have individual parameters of a custom object scaled non-uniformly.
Of course (but I'm sure you are aware, just mentioning for completeness here) such parameters can be scaled non-uniformly via the Attribute manager. Also you could implement handles for such, so the user can access these via the viewport. And the last option could be to implement your own scale tool.

I'm sorry, I know, none of these options is very convenient, but unfortunately I have nothing better to offer.

Cheers,
Andreas

@s_bach I've tried GetPlugin but even returning the BasePlugin pointer, GetName() was always empty for my custom baseObjects. Edit: GetName() works, GetTypeName() don't.

But GetObjectName() is perfect for me, thanks!

Thank you!
In future I will set the tags.

Omg! I had an old version of the plugin defined in the Plugins list in prefs that set the paths to [].
Blush Deluxe!
Sorry for wasting your time. Works perfectly fine.

Regards
Bonsak