@Cairyn Thanks again!

That's what I was afraid of, but thanks for the information!

Thanks, @Cairyn, that does work to copy the object and maintain the Layer link.

The problem I'm running into with it, is that if you run your code multiple times each time the Layer gets copied over again. With a Cinema copy/paste it would link with the first Layer instead of inserting a new copy of the Layer.

Would it be possible to duplicate that functionality?

Hello!

I'm trying to copy an object from one document to another using GetClone(), which works for that. But if I have the object with a Layer that Layer is not copied over to the new document. Is there a way to automatically copy the Layer along with the object?

User preformed copy/paste does bring over the Layer, but using this code it doesn't.

        // with two documents open and an object selected
        BaseDocument* activedocument = GetActiveDocument();
        BaseDocument* firstdoc = GetFirstDocument();
        
        BaseObject* first = activedocument->GetFirstObject();
        BaseObject* clone = static_cast<BaseObject*>(first->GetClone(COPYFLAGS::NONE, nullptr));
        firstdoc->InsertObject(clone, nullptr, nullptr);
        EventAdd();

Dan

@zipit Thank you for the info!

@m_magalhaes Sorry about that, Manuel. I'll make sure I do that in the future.

Dan

Hello!

I'm currently working on a Tag plugin that is linked to an object in the scene with a BaseLink, it is not the same object that it is currently on.

Is there a way that if the Tag was copied to a new document that the Linked object would also be copied over and inserted into the new file? If it wasn't selected in the initial copy command.

Dan

@r_gigante @kbar

Thanks for the infomation. I assumed that was the case and it makes sense, I'm just reluctant to stop supporting older versions of Cinema but it might be time.

Riccardo, I think I was using the incorrect version of osX or XCode, not sure which, but using your codesign worked when I moved onto a later version of both and it is correctly signing my R20 compiles.

Thanks both of you for all of the help and clarifying of notarization.

Dan

@r_gigante

Thanks for the breakdown!

I'm having trouble getting this to work:

$ codesign -f -s "Developer ID Application: <Your Name>" --options runtime <xlib file>

The terminal says that runtime isn't a valid argument.

Are there plans to have previous versions of Cinema running on Catalina and beyond or is it expected to only allow previous versions if macOS was upgraded?

I've been trying to get R14 plugins notarized, but XCode 4.4.1 doesn't build for 10.9 which is required for notarization. Does this mean its impossible to get R14 plugins loading in Catalina?

Dan

@kbar

Thanks for the information! That was the assumption that I was under.

I've tried notarizing the older versions of the plugins but I'll do some further tests and see how it turns out.

Dan

Hello Riccardo,

Following up about previous versions of Cinema in Catalina, I've been able to do more tests and I'm more confused now.

I've tested my plugins R15 and R18 on Catalina and in both of them my plugins fail to load because they aren't notarized. These are the same compiles that worked before Catalina. They worked through all previous OSXs. They worked from R14 through R20. After updating to Catalina fresh installations of the plugins are no longer working in R14 through R20.

Given these results it appears that everything needs to be notarized for Catalina.

Does this mean that it's impossible for plugins to work in anything earlier than R21 in Catalina or is something else the problem?

Dan