| Age | Commit message (Collapse) | Author |
|---|
|
|
|
For historical reasons lots of the code uses "xref" when talking about
a pdf document. Now pdf_xref is a separate type this has become
confusing, so replace 'xref' with 'doc' for clarity.
|
|
Remove the fz_context field to avoid the structure growing.
|
|
'marked' moves into the flags word. 'kind' becomes an unsigned char.
'sorted' moves from in the dictionary specific bit of the object into
the flags word. This should shrink us by 8 bytes.
|
|
When incremental update is in place, functions that alter one structure may
have the side-effect of altering another: i.e., updating an annotation may
require the Annots array or even the page to be cloned. This commit makes
the existing annotation code hardy to this eventuallity. It also cleans up
a slight mess of the past where not all annotation-altering functions had
access to the pdf_annot struture, instead having to work with just the
pdf object.
|
|
|
|
|
|
* at one place, code returns from inside an fz_try which borks up the
error stack
* pdf_load_xref wrongly assumes that at least one non-empty xref has
been read if there were no errors thrown during parsing
* pdf_repair_xref skips integers when object numbers are out of range
|
|
|
|
|
|
Had to rejig the thumb entry/exit veneers to allow for NDK_PROFILER
operation, but this seems to have negated the need for Core2.mk, so
removed that here.
|
|
|
|
Match our naming conventions.
|
|
|
|
|
|
|
|
Fix of logos and icons to match Android and iOS applications.
Switch to using DLL for the mupdf winRT library. Static libraries for
winRT defined calls is not allowed. Added linker options for security issues.
Also fix of some circular header/namespace issues.
|
|
|
|
Various tweaks to ensure the exception handling works as expected
when throwing error values. The key thing is not to reset the
error value on a try, as this can cause problems when code calls
trys in the always section.
|
|
|
|
|
|
|
|
|
|
file activated.
Also fixed a few issues for when we open a new file and close the
current contents. There was an issue with the displaylist cache
clean up.
|
|
In preparation for work on progressive loading, update the exception
handling scheme slightly.
Until now, exceptions (as thrown with fz_throw, and caught with
fz_try/fz_catch) have merely had an informative string. They have
never had anything that can be compared to see if an error is of
a particular type.
We now introduce error codes; when we fz_throw, we now always
give an error code, and can optionally (using fz_throw_message)
give both an error code and an informative string.
When we fz_rethrow from within a fz_catch, both the error code and
the error message is maintained. Using fz_rethrow_message we can
'improve' the error message, but the code is maintained.
The error message can be read out using fz_caught_message() and the
error code can be read as fz_caught().
Currently we only define a 'generic' error. This will expand in future
versions to include other error types that may be tested for.
|
|
Also correct a comment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Patch from "andyhan2000" to make the ink annotations smoother.
|
|
|
|
Tested with msysgit 1.8.3 environment.
|
|
|
|
Just before pushing the previous commit of Michaels, I removed
an fz_var, thinking it wasn't required. After discussing it with
him I realise that it was needed, so reintroduce it here with
another error handling tweak. Apologies!
|
|
|
|
Also rework of some UI interactions to avoid zooming, text search, etc when
in a specialized view like contents or reflow (webview)
|
|
The display list rendering is used when scaling within the current page to
enable quicker response.
|
|
Thanks to zeniko for spotting these.
|
|
Spotted by Vincent Torri. Many thanks!
|
|
Remove fz_free_display_list from the API; instead use fz_drop_display_list.
|
|
In some cases, the existing code can leave the GLYPHCACHE lock held
if an error occurs during type3 rendering. Correct this oversight.
Thanks to zeniko for spotting the bug and providing a fix.
|
|
When creating the previous commit, I considered an alternative way
of working. While we didn't use this in the end, I forgot to remove
it from the code before committing. Stripping it out here. Sorry.
|
