Keynotes ghost conflicts

[Lucian Laculeanu]

So... We are in the second (basic number) iteration of the software using native Keynotes tool.

When are we going to not have the issue of ghost conflicts?

Why do we have to still go through endless maneuvers of deleting, exporting, updating hotlinks, saving, re-mapping and re-importing to clear this issue?

Is this going to be solved by the time I see 4 in the beginning of the AC issue, or should I hope retirement will make this issue dissapear for me?

Operating system used: Mac Intel-based Tahoe 26.5.2

[Barry Kelly]

Are there other posts here that describe this issue?

Have you reported it to your local support?

Barry.

[Ignacio Azpiazu]

[I never used Keynotes, but:] I asked GPT and it says the Keynote database can be brought from one file to the other, similar to attributes with Attribute Manager, but through the Keynotes palette.

Is it then any different from attributes in multi-file projects, where you want to have one file that is the master for attribute management, in which you create new attributes or into which you bring in any intentionally or accidentally created in the other files, and from which you overwrite all the other files whenever there is a conflict (and yes, republish and update modules)?

https://chatgpt.com/share/6aa74e34-0898-83e9-b5ab-12533b513749

[Lucian Laculeanu]

@Barry Kelly It is a bit worrisome that my post is the first one on this issue, since it is not isolated to my project(s) and environment.
A shortcut that works most of the times is exporting the set you want, import in all hotlinks if used, close hotlinks, delete keynotes from "central", update hotlinks and then re-import... But the remaining "sometimes does not work" are the frustrating happenstances.

@Ignacio Azpiazu Nice to see you around here my friend! All other bases are covered 🙂 Thank GPT for me

[Barry Kelly]

@Lucian Laculeanu 

The reason I asked if there were other posts is so I could merge this one to them.

Keep it all tidy.

A quick search of "+keynote +module" didn't seem to find anything interesting.

I am sure I have read something somewhere, I just can't remember where.

But if this is the first time it has been talked about here, then could you provide more detail on what a 'keynote ghost conflict' is and maybe show some examples.

I know how keynotes work, but I have never had the need to use them.

Especially not with modules.

I would assume like attributes. the keynotes in both the master file and module file should be the same, otherwise conflicts can be expected.

Barry.