Using PDOCG in Reader plugin

Question

Hi
the PDF plugin API documents say that the PDOCG calls, e.g. PDOCGCreate and PDOCGSetUsateDictEntry are available for all products.
I have some plugin code which works fine in PDFL and Acrobat, but is failing in Reader.
As an example, the call
PDOCGSetUsageDictEntry(ocg, ASAtomFromString("View"),usageDict);
works fine in acrobat and PDFL, but throws a "This operation is not permitted" when the plugin is running within Reader.
Are the PDOCG calls subject to reader extensions rights being set on the document?
If so, which rights need to be set to enable these functions to work.
thanks
-r

Answer 1

A bit more information, as I know every little bit helps...
1) Looking at the doc "modify" permissions
  status = PDDocPermRequest(pdDoc, PDPermReqObjDoc, PDPermReqOprModify, NULL);
i see the following.
a) within acrobat pro:
  standard pdf file       - modify=YES (status == 0 )
  reader-enabled pdf file - modify=NO  (status == -1)
b) within Reader
  standard pdf file       - modify=NO
  reader-enabled pdf file - modify=NO
note that within acrobat pro, the reader-enabled file has the modify 'right' disabled,  which suggests to me that this right has been REVOKED by the ReaderExtensions server.  Is this how it works?
2) running the same plugin within acrobat pro, my calls to create the OCG and set the usage dict
work fine for the standard pdf file, but FAIL for the reader-enabled file.  Makes sense given the PDPerm results above.
This leads me to believe that it is the same modify=NO setting (within reader) which is causing the
method calls the throw the "operation not permitted" errors stated earlier.
The rest of my watermarking code is modifying the document without any problem whatsoever, so does this
Mean that i have to resort to more grubbing around using Cos api calls to achieve this?