@mp5gosu
Thanks for the clarification.

@cairyn
You are right.
I thought having to go over the BaseContainer obtained from the object via GetData(), but didn't see anything in its content related to the displaycolor ... didn't think of just accessing the object's properties directly. I am not that confident with the Python SDK.
Thanks for the piece of code.

@r_gigante
Thanks for this. It ticks all the boxes for me.
Although I had hoped for a solution with less batch files, I now understand it's better to have separate batch files per plugin. And one for updating the project solution, without updating every plugin.
So obvious it's embarrassing, but some... ,ok, most times I need someone else to show me the obvious.

Still wondering about @mp5gosu 's answer.

Thanks again Riccardo.

The C++ SDK does have BaseObject::GetColorProperties to obtain the custom displaycolor assigned to an object. This seems not to be available in the Python SDK.

Hi Riccardo,
At first sight I thought "but of course, why didn't I think of that".
But on second thought, the whole purpose of running the Project Tool is because I need to add a new plugin to the solution.

So, I actually don't need to update a single plugin project, but need to update the solution project ... well, I mean, the project containing the solution.
As far as I have understood I would these need to run the Project Tool on /plugins/ which will thus update all plugins' projects.

Well, it turns out I was using an "old" Project Tool. Went over the documentation once more and downloaded the latest version. Ran it ... and custom settings (post build, source folders/filters, ...) all gone, again.
Fortunately, the debug options (location to cinema executable and g_alloc=Debug) remain as is. So, at list not everything gets cleared.

Apart from that I don't see what I am doing wrong, just launching the projecttoo.bat file containing:

d:\Projects\dev\SDK_R20\projecttool\kernel_app_64bit.exe g_updateproject=d:\Projects\dev\SDK_R20

Edit: going over the documentation again since months, I now see that removing "g_updateprojects", as mentioned in my previous post, would have been rather silly.

Thanks Riccardo,
It all (well, some of it) starts to make sense after your explanation. A big step forward in starting to understand how to proceed with the MAXON API.

Just launched the projecttool again ... custom settings are overwritten once more.
Am I using an old version of the projecttool maybe?
Or should I remove the "g_updateproject" argument?

Also, I keep a backup of the plugin (source, res and project folders) in a subfolder of the plugin.
Obviously, the projecttool does process all subfolders. As such my backups are also updated.
Any change to set up the projecttool to ignore these subfolders?

In Visual Studio I have added per plugin a custom post-build-event. This copies the resources and compiled plugin file to its specific location, overwriting the previous build. Using this setup, I can include the plugin path in Cinema 4D, which will then load the copied plugin.

However, when adding a new plugin to the projectdefinition and using the projecttool, all project files are updated and these custom steps are lost. Same for the folders/filters I create to organize the different source files in each plugin.

Is there a way to skip/avoid updating some plugin projects, without removing them from the projectdefinition file, as I still want these plugins part of the main Visual Studio solution?

Hello again,
It's been a while ;-)

I am currently still using the classic API for all plugins, and was looking into creating small "learning" plugins using the new API. Wanted to do so with baby steps, so I thought first to use the classic API for the main framework of the plugin (using PluginStart and the regular registration methods) while using some functionality of the MAXON API.
Not sure if this is even possible, using a mix of classic and new API.

For a first "learning" plugin I though to keep it simple and implement a plugin that has no interaction, but simply displays some information (in the console) when Cinema4D starts.
So, I thought of displaying the MAC address.

From the legacy forum I found a way to do so using the classic API
https://plugincafe.maxon.net/topic/10754/14198_how-to-get-the-ethernet-id-list-solved

And since GetMacAddress doesn't seem to be available in classic API of R20, that's a good opportunity for a learning experience. Well, there seems to be a Machine class which contains GetMacAddress, but haven't found a way how to use that.
And since the purpose was to use the MAXON API I looked further and found NetworkAdapterInterface.
Went looking for information on interfaces, implementation and usage, but examples on GitHub weren't useful. I just cannot wrap my head around it.

The cinemasdk has examples for tool plugins, object, shader, ... These all are resources to learn from. Aren't there any full plugin examples using the new MAXON API? Or have I been looking at the wrong place?

To be honest, first steps into the new API were quite frustratingly overwhelmed.