> > So, my question now is what is a "proper" fix? I can think of a few > alternatives: > > 1) Wait for PoDoFo to make a formal code change that helps my situation. > > 2) Continue to use a hacked PoDoFo (not a problem right now, but not > desirable long term). > > 3) Extract the relevant logic from PdfAcroInit() and embed it directly > in my own code (risking my code breaking in the future if PoDoFo makes > an incompatible change). I have not fully researched this > alternative. At this time I don't know if the methods invoked by > PdfAcroRead::Init() are "public" such that I can invoke them myself > directly in my own code.
I have successfully implemented option #3. However, if this is not he best long-term approach, please let us know. Thanks! ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
