Hello. In addition to @zipit's excellent answer, you might consider also implementing a Message Plugin and react to CoreMessages, sent via c4d.SpecialEventAdd()
May I ask for practical examples on where you have seen this behavior?
There are actually some tags with GUI interaction. The MographCache Tag for example.
You are calling the Dialog via DLG_TYPE_MODAL. So the Dialog is blocking the main thread until you close it.
Try opening the dialog with DLG_TYPE_ASYNC.
@ilad Well, it's not limited to non-animated objects. As @r_gigante posted, you're actually modifying the points and the matrix. Both operations can also be achieved manually. So, no difference if animated or not.
The only thing you have to keep in mind when modifying animated objects is to make sure, all keys containing Matrix/PLA data have to be handled as well.
Hi iLad,
primitives' axis cannot be changed because their geometry is parametric and generated by the object itself. If the object doesn't come with the function to change the axis, there's no chance to change it via code either.
However, if you have polygon objects, you simply move all points in a desired direction.
For example: If your cube is 200cm in Y dimension and the axis is centered, you simply add Y = 200/2 = 100cm to all points. Then you move the axis/object into the opposite direction for the same value to compensate the position.
You may want to try ExecutePasses() - that command will animate the current frame of the document and therefore works like scrubbing the timeline.
Yes, I'd like to see it of course. Maybe you can share it via Github so others can for and contribute to it. :)
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.
I'd like to add that using GeListNode and GeListHead is convenient since they already come with all functions you need.
Ah, I somehow overrad that the cinema4dsdk worked.
I'm actually out of ideas here.
And yes, it cann occur that plugins compiled with higher version than the one the plugin is installed to won't work at all.
I assume, you are using different versions. Check, that you both use the very same SDK version that comes with any C4D installation/update.