Persistent Data on kTextStoryBoss

Question

Hi Folks,
I've written some code to add persistent data to a story/text model. This has involved adding my Interface\implementation to the kTextStoryBoss as follows...
AddIn
    kTextStoryBoss,
    kInvalidClass,
        IID_IMYINTERFACE, kMyImpl
with the class set up as follows...
// Binds the C++ implementation class onto its ImplementationID making the C++
// code callable by the application. 
CREATE_PERSIST_PMINTERFACE(MyImp, kMyImpl)
I've also added the appropriate scripting code to allow the data to persist when a document is exported as IDML or a text frame added to a library. The provider element defines the object as kStoryObjectScriptElement.
resource VersionedScriptElementInfo(2)
     // Contexts
          // Scripting support added at InDesign CS 2.0.
          kFiredrakeScriptVersion, kCoreScriptManagerBoss, kInDesignAllLanguagesFS, k_Wild
     // Elements
          // Specifies a property.
          Property
               kMyPropertyScriptElement,
               p_MyTextData,
               "my text settings",
               "Describes my text settings",
               StringType,
               kNoAttributeClass
          // Connects this plug-in's methods and properties to scripting.
          Provider
               kMyScriptProviderBoss,
                    Object{ kStoryObjectScriptElement },
                    Property{ kMyPropertyScriptElement, kReadWrite }
So testing was producing the required results until I tried copy/pasting or duplicating frames. In both cases non-default values in the data won't persist - the new frame just contains data in its default state.
This is a major problem. I'm sure when I first investigated persistent data against the kPageItemBoss, the data was copied correctly when the frame was copied. So I'm baffled why this isn't the case for stories.
Is there a simple way to overcome this? I was wondering if it could be done via a LazyUpdate\Update call in an observer or via a responder. Trouble is that I can't find anything I should attach to (or respond to) to allow me to copy the data from the original frame to the new one.
I could fall back to using kPageItemBoss, but then you have to account for threaded frames (which I can handle) and the fact that the data will be persisted against image frames. But I'd rather not do this if possible.
Cheers,
Andrew

Answer 1

Hi Dirk,
Thanks for the suggestions, I had a look at them but I don't think they will help.
IReferenceConverter
If I understand you correctly, this interface can be implemented as long as my persistent data is stored in its own boss. I had a look at the PersistentList SDK sample, which backs up what you have stated (that the persistent data kPstLstDataPersistImpl would be defined as part of a new boss kPstLstDataBoss). But that would suggest adding one or more implementations (i.e. command bosses to create or manipulate that object).
My code simply adds kMyImpl to kTextStoryBoss. The code in my supporting facade simply allows me to get at the persistent data via the text model.
     InterfacePtr<IMyData> ptrData(ptrTextModel, IID_IMYINTERFACE)
Also I got the impression that its use is primarily to take an existing object and copy it to a new database. For example if I had a colour object used by Object A, the IReferenceCounter interface would make your new copied object (Object B) reference the existing colour object rather than create a new one - as the name of the interface suggests! In my case that means a modification to my data on Object A would also apply that modification to Object B. I'm looking for a full copy.
kNewStorySignalResponderService
Had a look at the interface for this one too. It looks like it's only for the creation of new stories - I'm looking to copy the data to the new story from an existing one. The interface suggests that you can access the UIDRef for the new story and that's it.
At the moment Dirk it looks like it's going to be persistent data on page items!