More about app.openDoc

Question

Hi,
being a bit further with my work on app.openDoc thanks to the help of this forum, I'm a bit puzzled about the following problem:
var mainDoc = app.openDoc(mainDocPath);
//var mainDoc = app.openDoc("/C/myDoc.pdf");
app.alert(mainDoc);
In this example "mainDocPath" is a valid path and the document opens. Anyway mainDoc is being evaluated as "undefined".
When I use the commented line instead, the alert displays "[Doc_Object]" as I would expect.
What is going wrong here?
Thanks for any help.

Answer 1

I have been breaking down complexity a bit further.
Two documents: C:\Control.pdf and C:\Main.pdf.
The control document has a document level javascript "TestCall" with content:
function TestCall() {
    mainDoc = app.openDoc("/C/Main.pdf");
    //this.closeDoc();
TestCall();
The main document has a javascript "SetDisclosed" with content:
function SetDisclosed()
    this.disclosed = true;
When I run the control javascript while the document is open, everything is fine and it opens the main document. If the javascript runs on document initialization, I get the "NotAllowedError".
If I change the line "mainDoc = app.openDoc("/C/Main.pdf");" to "mainDoc = trustedOpenDoc("/C/Main.pdf");", i.e. running the folder level script
trustedOpenDoc = app.trustedFunction(
     function(pPath) {
          app.beginPriv();
          var trustedDoc = app.openDoc({
               cPath: pPath,
               bUseConv: true
          app.endPriv();
          return(trustedDoc);
everything is still fine when run from the opened control document.
When it runs at document initialization, I get an error dialog stating that an error occurred when opening the document because of an "invalid action object" (this is in german language and I don't know the exact words that it will show in an english language version).
That can't be the intended way of functionality, can it? When reading through the forums, I get a feeling like many people do what I want to do and there is only one more little hint missing and there will be prospering landscapes for my programming efforts if this could be solved. Unfortunately I can't find the point myself and can't see sense and meaning in that ugly behaviour.
I already had the idea that the folder level scrips might not already be loaded when the trusted function is called at document initialization and tried it in a loop with a try/catch construction, but it was never working at document initialization.
Any more hints?