R20 uses a new scheme: https://developers.maxon.net/docs/Cinema4DCPPSDK/html/page_maxonapi_plugin_dev.html#page_maxonapi_plugin_dev_resources

Like @Cairyn said, it's the workplane.

How do you import the ZBrush project?

Hi there,

since the docs say you get the selection instance by calling GetBaseSelect(), you simply can modify the BaseSelect and update the object accordingly.
The BaseSelect itself comes with some useful functions, like CopyTo() that may do what you want.

And may I to point you to: Q/A functionality and How to post questions. It makes life easier for all, if new threads and questions are tagged and organized in a nice way. :)

For custom nodes, check this thread here: http://www.plugincafe.com/forum/forum_posts.asp?TID=9631

For using GeListNodes, etc. I currently don't have a minimal example. But let me try to bump you in the right direction.

The TreeViewCustomGui uses a root object. This root is so to say a "container" that holds your list structure. This can be anything - you are then responsible to handle all the actions within the TreeViewFunctions, like GetNext(), GetDown() and so on. It is entirely up to you what you deliver to these functions. This level of abstraction comes with great flexibility.

If you want to go for GeListNode, the following may work for you:
Create a GeListHead - this is your root.
Fill this root with GeListNodes as you desire.
Then, hand the root over to your TreeViewCustomGui via SetRoot()
And now, in the TreeViewFunctions, all you have to do is handle the nodes.

So, if you can go a bit into detail, we should be able to pinpoint a solution.

If you have any questions, I'll be happy to help. :)

edit: By the way, you may want to start with BaseList2D instead of GeListNode since it already has SetName() / GetName() implemented and also supports selection bits. This is a bit easier to start off if you want to experiment.

If you want your items to behave like GeListNode, you either have to create a custom node that implements linked-list behaviour or - what I recommend - use GeListNode or Baselist2D directly. Another approach - but that highly depends on your goal - would be to use NodeData plugins.
I tend to use them just as list nodes and give them "payload", since they are just representations inside the TreeView and already come with all functionality that you need. Plus: You get the same functionality as with all other objects that derive from them within Cinema 4D.

The delay may be caused by the fact, that c4dpy is actually some kind of a headless Cinema 4D installation.
So, everything that is core part of C4D is loaded, that may take some time.

Also, PyCharm tends be slower launching all debugging subsystems compared to VS Code.

@m_magalhaes Huh, nice. But is this documented somewhere?

edit: Nevermind, found it. :)

Hey mike,

you can use a parent group with 3 columns layout and then for each column, put it into a speparate group to maintain constant width.

Imho, just call it plugin component. :)

It's actually the axis and the points that have to move.