Multiple document use of field.buttonSetIcon(...) is failing

Question

We're trying to store a set of icons in a pdf document that can be shared by all the attached pdf documents.  The result of this would be then when we are in one of the attached documents (call it the child), we can read the icon from the parent document, and set it to a field created on the child document.  Here is the sample of the JS we're using ("this" pointer is for the child document)
    function CreateWidgetWithIcon(box, iconname)
        var name = \"NewWidget\" + this.numFields;
        var master = GetRootDocument(); <-- this function returns to us the document that contains the icons
        var field = this.addField(name, \"button\", 0, box);
        field.buttonPosition = position.iconOnly;
        var sourcefield = master.getField(iconname);");
        var icon = sourcefield.buttonGetIcon();"
        field.buttonSetIcon(icon);
All the functions are returning exactly what we expect them to.  If the this.addField were changed to master.addField, the exact result we want happens, just in the wrong document.  But when this is run in the child document, and we try to create the field in the child document, when the icon is set to the field, we get:
    GeneralError: Operation failed.
    Field.buttonSetIcon:8:Bookmark undefined:Mouse Up
Both document are open and disclosed when we run this.
Is this an expected failure?  Is it possible at all to have a resource that is stored as part of one document but accessed by another?  ImportIcon and buttonImportIcon don't seem to fit our needs either as I need this to be an entirely self contained document, deliverable as one pdf.

Answer 1

Getting and setting button icons within the child document works as expected, as long as the button originally existed as a resource of child document.  I've not had any luck copying the icons from the child to the master either.
When we try to doc.addIcon on the other document, the call silently fails, returning null.
We tried the global variable options.  I wasn't aware you could use variables other than bool, number, and string.  We'll have to see if we can put this to good use now, but even so, this doesn't gain us anything in this instance.  We've always had access to the icon object in the child document.  When our JS is executing, we have both a "master" and "child" doc as variables.  In both of these, we're able to add and get fields, get and set icons, etc.  So when we're in the child document, we still have an Icon object that we got from one of the master's fields.  In this case of adding it to a global and then retrieving it from the global, the variable hasn't changed any, and is thus the same variable we would have access to if we didn't put it into the global first.  When passed through the global object, the same error as before is still returned.
The WindJack (awesome tool, we love it) and FormRouter tools only deal with IconStreams.  All these techniques and tricks do seem to be helpful in those scenarios, but IconStreams can be created from Icons, but not the other way around, thus these other tools aren't particularly useful to us.  If we could find a way to use an IconStream to make something appear within our document, then we could work with that, but I've tried and haven't been able to get any of that to work.  Our best results for the appearance we desire for our annotations is to user button fields and to use Icon objects to set the appearance of them.  We're open to other methods, but really, we would just want Icon to work.