?? When reading from a stream, not all info is read ??

[DSSavant]

Yea, I'm kind of guessing what is going on here. I've attached a Zip file that has a sample PDF file and a README that fully explains what I'm doing and the code I'm using.

Bottom line, when using the viewer control to read a file via streams that has been updated and then saved on top of itself, it is rendering and responding differently than the Tracker Viewer or Acrobat. Responding differently meaning that it is rendering the prior version of the file (before the last save) as well as executing JavaScript against a prior version.

Big Note: When saving the file using Save As, meaning that Acrobat has written the file out from scratch, all works as it should.

Sounds like a cool bug huh? LOL. Scream if you need anything else from me.

Please see attached ZIP file.

[Vasyl - PDF-XChange]

Hi, DSSavant.

We investigated your problem. Thanks for detailed description.
But we can't reproduce the described bugs with the current version (2.5.0.192) it works/renders correctly and identically in our EU-program and viewer-control.
Maybe you are using an older build...

About loading/saving from/to stream:

I think these bugs are not dependant on streams usage, our viewer-control loads the entire data from the stream before document opening, and saves the
entire data to the stream on document saving.

Best
Regards.

[DSSavant]

I will research more. I'm guessing it is a setting I have set in the viewer. I'm running 2.5.190.

[DSSavant]

I have reproduced this using the C# Full Demo application that Tracker ships with the SDK. Since I'm two builds (or so) off of the version you tested with, I upgrade and test again - I'm currently waiting on a build that should be released today/tomorrow.

[John - Tracker Supp]

Ok - thanks - should be up later today ...

Cheers

[DSSavant]

Just got the new build, 193, loaded.

Problem fixed. I'm also seeing more verbs to play with in the documentation. It's almost like Christmas!

[Paul - PDF-XChange]