@ferdinand
Hello Ferdinand,
Thank you very much first of all.
yes, you're right, I worked extremely sloppily with the SMC method, of course I'll take the threading into account and also work with a Temp Document.

Regarding the problem itself, I can only say that reinstalling CINEMA 4D solved our problem.

Cheers

Hi Illia,

I haven't been able to properly stress test the new code, but by the first look it seems to be working. Thanks!

Dan

Hello @justinleduc,

Sorry for the delayed answer.

You have a point that the discussion on some abstract questions doesn't require any code. However, you have a very specific question, namely you're struggling from your cursor constantly flickering between cursor states. This is your exact code that produces this undesirable result, so this is not an abstract question.

According to my observations there's no issues with flickering cursor in GeUserArea in C4D 2024.2. You can find some good examples in our C++ repository. for example you can start with C++ SDK - Example Dialog. Please also make sure you familiarized yourself with the following manual pages:

GUI and Interaction Messages Manual GeDialog Manual GeUserArea Manual

Especially the GeUserArea::Message() would be something of your interest.

If you're still observing the issue please provide a minimal code snippet that gives context to our discussion.

Cheers,
Ilia

Hey @ThomasB,

That has nothing to do with the highlighting but with the fact that Maxime used incorrect links. developers.maxon.net/docs/ links will only work from outside of the forum. Inside the forum you currently have to use dvelopers.maxon.net/assets/docs/ as otherwise nodebb is trying to take over the routing. I am working on fixing that issue.

I have fixed both links of Maxime.

Cheers,
Ferdinand

@ferdinand thank you for your welcoming words, for your help and edits.

Since I am no trained developer I was simply copy and pasting my first lines of code including the RegisterCommand function from the maxon python example github and thought it would fit my application since I thought the description in the sdk seemedlike a match to me ["Command can be dragged into an icon bar and delivers its own dialogs instead of icons." (- maybe I got that wrong)]. Also scince I have little developing experience the term "smallnode" is nothing I can make sense of and an accurate description seems to be missing.

Nevertheless I tried your suggestion and it works like a charm.

Thanks a lot 🙌
Marc

@m_adam Thanks!👍

Thanks a lot for the clarification! It would be nice to include more usecase examples of GetAccessedObjects(..) implementation in the SDK examples in the future. I will try your suggestion once 2024.4 becomes available.

Hey @m_adam ,

Thanks for your help. It works now.

However, I'm wondering how I would have known that I needed to set the scaffold ID to the node. The documentation doesn't seem to explicitly mention this step. I might be wrong, but for someone without strong knowledge of the API, I'd never thought that way. I would rather added the selected nodes to a group, as this is what a scaffol is. Does that make sense?

As a side note, after adding the nodes to the scaffold group, they appear messy, actually the nodes are nicely arranged inside the group, but the scaffold is overlapping other nodes. This is likely related to the bug we discussed here: https://developers.maxon.net/forum/post/73446. Am I right?

Cheers

@ferdinand, Is it possible to VertexColor, WeightMap(character rig) in the same way?
Some games use VertexColor, so marking can always be useful.
I tried to convert your code to VertexColor, but I lack knowledge. Please help us.

The API does appear to have movie saving features. https://developers.maxon.net/docs/py/2023_2/modules/c4d.bitmaps/MovieSaver/index.html

Hi @ll2pakll ,

Please excuse the delay, your topic somehow slipped from my list.

I can only speculate here, as you haven't attached a sample scene that highlights your issue.

The way you describe the problem it looks like a priority issue of the python tag. Please have a look at how the priority works in our documentation: https://help.maxon.net/c4d/2023/en-us/Default.htm#html/TPYTHON-OBASELIST.html#EXPRESSION_PRIORITY

Also note that it's forbidden to call c4d.EventAdd() (or in reality is just skipped) from the python tag due to multithreading restrictions (c4d.EventAdd() is executed on main thread whilst python tag is executed in a parallel thread):
9ddbfeab-53dd-49e1-8ded-0a6c3dddba94-image.png

Cheers,
Ilia

@ThomasB said in How to create python plugin in 2024?:

Yes, download the SDK and study the examples.
I wrote my own software that allows me to simply select the type of plugin I want to create, enter the plugin ID and the plugin name. The program then creates the folder structure, all files with the correct content and the correct name automatically...that was the first thing I did because it is always extremely tedious.
This then takes 10 seconds and I have a finished blueprint. Then I can start programming straight away.
I usually make the Gui first using UserData to roughly create the design and then I write it down in the resfile in no time at all. It's relatively quick and even fun and you gradually grow into it, it emerges little by little.....

Basically it wouldn't be a problem to write a script that writes the UserData interface into a Res, header and string file, I already have an idea for that... That would actually be easy to do.
I'll get to it when I'm done with my update... and then maybe make it available to the community... However, a similar one is already there, but I can't remember where.

Greetings
Tom

Yeah, that sounds cool. The ui stuff you're mentioning was very similar to how the old ResEdit plugin worked. the source code is on gitHub, but I don't know how to compile C++ plugins.

But I guess there is nothing there. This stems from me copying one of the examples from the Python SDK and trying to make it my own. It hasn't been very intuitive for me, which is why I asked because I figured I must have been missing something, but it seems I am not.

Hi @m_adam,

thanks a lot, that did the trick.

To close this topic off here's a snippet to allow other objects but not the current object to be dropped in there:

def Message(self, node: GeListNode, type: int, data: object) -> bool: if type == c4d.MSG_DESCRIPTION_CHECKDRAGANDDROP: relevant_id = c4d.DescID(c4d.YOUR_PARAM) # Use the ID of the parameter of your object that you want to check. current_id: c4d.DescID = data['id'] if relevant_id.IsPartOf(current_id)[0]: dragged_element = data["element"] is_same_object = node == dragged_element data['result'] = not is_same_object return True return True

Cheers,
Daniel

Hi Daniel,

You cannot include multiple containers and keep their IDs different. There's no special arguments for the INCLUDE statement that can optimize this workflow for you.

In your case having your own implementation of CYCLE would be the solution you're looking for.

Cheers,
Ilia

Hi Maxon team,

Just want to bump up the issue, which is still here under the Cinema4D 2024.2

Hi Maxime,

Thank you very much for looking at my issue.
Did you try the new function ? I've added it in my code and unfortunately I get the same result as before.

Cinema_4D_3JwcCopDUD.gif

Hi Maxime, thank you very much for your answer! I wasn't sure if storing things in the global document BaseContainer was a good approach, but it's working well.

Cheers,
Daniel

Hi you are right, I double checked and my c4d_string.str was like that, sorry I copy-pasted your in my reply without notifying it.

// C4D-StringResource // Identifier Text STRINGTABLE { PLuginName "AAAAAA-ROUNDED Tube"; }

All the rest is correct in your sentences.
Cheers,
Maxime.

Hi @baca, sadly it is not possible to get the exact same random in Python than the one used internally for this feature. So the only way would be to actually clone some objects an retrieve their position as shown in read_modata_color.py. The previous example retrieve the color and not the position, so instead of retrieving the MODATA_COLOR, use the MODATA_MATRIX.

Cheers,
Maxime.

Hi @BretBays this is correct, if you want to make a Brush the easiest way is to register a SculptBrushToolData , you can find examples in Python in Github or in C++ in Github.

SculptBrushToolData is derived from DescriptionToolData, meaning they can have a description visible in the attribute manager and therefor you can add your own checkbox if needed.

Cheers,
Maxime.