HI Bentraje, thanks for reaching out us.

With regard to your request, I'd like to share few considerations:

• tags can store relevant information for the scene (whether they are visible or invisible)
• tags can be hidden and avoiding copy of visible ones will also prevent the hidden ones to be copied

Because of the above considerations, cloning an object without its tags can be risky and lead to unpredictable results.

That said you can attempt to delivery a clone without tags by using the COPYFLAGS::PRIVATE_NO_TAGS but aside from this non-officially supported approach, disclosing your final intent might be more helpful.
Can't you consider for example to clone everything and then to remove those tags you know that to your scope are useless?

Best, Riccardo

Thanks a lot @AndreAnjos for sharing the code.

I'll try to have a look at it and maybe contribute if/where needed. For the time being I'm glad to hear that you were able to tackle with it.

Cheers, Riccardo

Hi @rsodre, thanks for reaching out us.

In order to avoid doing too much speculative work on understanding the issue, can you please make a short video showing it and share the scene in order to replicate it here?

Thanks, Riccardo

Hi @mike, thanks for reaching out us.

With regard to your question, I encourage to have a look at the cinema4dsdk on Github examples where on the customgui_string.cpp both methods are properly implemented (see here).

If the example isn't enough to bring you on the right direction, please provide us with some more details (code?) in order to look at your implementation.

Best, Riccardo

Hi Bentraje, thanks for reaching out us.

With regard to your request, I confirm that it's not possible to programmatically fold/unfold a generic manager being the API involved in controlling the managers' behavior not exposed. In addition, being possible to open multiple managers (of the same or of a different type) at the same time it's currently impossible to identify on which windows to execute the fold/unfold task.

Best, Riccardo

Hi @mikeudin, thanks for reaching out us.

With regard to your request, although it's not expected it to work inside the Cinema 4D Script Manager you can get it properly working using the c4dpy executable (here's the 20.059 compatible version) as much as you do on the Python Shell or on SublimeText console as you can see from the log below.

$ more test.py
import inspect
# Save this code as script py-file and start

def main():

  code = inspect.getsource(main_new) # place function code to str variable
  print code # print code text. Works on Python Shell, but not in C4D Scripts Manager

def main_new():
  # This is a comment
  # New comment string 
  # Change this code, to check the console output
  pass


if __name__ == '__main__':
  main()


$ ./c4dpy.app/Contents/MacOS/c4dpy test.py 
def main_new():
  # This is a comment
  # New comment string 
  # Change this code, to check the console output
  pass

$

Best, Riccardo

@Passion3D I see your point about being disappointed on not having VisualStudio for Mac supporting C++ but it's the status-quo and we can't do anything to change it.
With regard to the link you've pointed it actually refers to Visual Studio Code which is indeed a different product compared to Visual Studio for Mac and Visual Studio.

@janbiko even modifying the CMakeList.txt file in order to support Apple platform at the compile time, C4DImporter.cpp refuses to compile because it has been designed only to be compiled under MSVC. And this is another reason to check with AssImp community for bringing the required changes.
Last but not least AssImp looks to support only Melange 16.x.x which is five revisions older than the current one. It could happen in the end that due to the changes that Melange has undergone in the course of these years compatibility might break up.

Hi @Graeme, thanks for reaching out us.

With regard to your request, aside from the @mp5gosu notes I'd like to point you to this discussion where SelectionTag creation is presented.

Feel free to come with any further consideration.

Best, Riccardo

Hi @bentraje, thanks for reaching out us.

With regard to your question, there's no "straightforward" method delivered, either in Cinema 4D Python API or C++ API, tailored to this specific scope but rather using the approach proposed by @Cairyn is the way to go (and personally I don't find anything clunky).

With regard to the GeListNode::Remove() as reported in the documentation it's just responsible for removing a node from a list and in C++ it's also return the object's ownership to the caller freeing Cinema 4D from being responsible to dispose that resource.

Best, Riccardo

Hi @mike, thanks for reaching out us.

With regard to the issue reported, I confirm that it's known bug and there is no current workaround.

A bug fix will be delivered in the future.

Regard, Riccardo.