summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-02-21Use a fixed duration of 400ms for scroll animation.Tor Andersson
Make fade in/out animations 200ms long, the same as the default animation duration for iOS UI animations.
2012-02-21Android app: decode the uri before using as a file namePaul Gardiner
2012-02-21Remove android/local.properties from the git.Tor Andersson
Seeing as it has local configuration, it should not be version controlled. The android manual says so.
2012-02-21Android app: make taps on side margins move to next and previousPaul Gardiner
2012-02-21Android app: implement Tor's request to clamp vertical position when height ↵Paul Gardiner
within screen
2012-02-21Go back to using a direct fade animation in favour of the ViewAnimatorPaul Gardiner
2012-02-20Android tweaks; attempt to trigger on .xps and .cbz files too.Robin Watts
In theory, the changes here should make mupdf be recognised as a handler for .xps and .cbz files (and for .pdf files without the correct mimetype). In practise I can't actually make this work right on my device. I'll open a stack overflow question and ask there.
2012-02-20Remove "MuPDF" title bar on Android app.Robin Watts
Simple change to the XML.
2012-02-20Update android app to use document interfaceRobin Watts
This adds XPS and CBZ support for free.
2012-02-20Updated MuPDF Android app from Paul Gardiner.Paul Gardiner
2012-02-16Remove mupdfdraw and muxpsdraw in favour of mudraw.Robin Watts
No other code changes.
2012-02-15Check determinant before inverting a matrix to avoid division by zero.Tor Andersson
2012-02-15Stop searching in viewer when clicking page links.Sebastian Rasmussen
2012-02-15Add braces to resolve ambiguity.Robin Watts
2012-02-15Fix typo in comment.Robin Watts
CLUSTER_UNTESTED.
2012-02-15Treat 0000000000 * n xref entries as free ones.Robin Watts
Quartz generated PDFs (and maybe others too) seem to use 000000000 65536 n to mean "free object" in defiance of the spec. Add special case code to mupdf to handle this.
2012-02-14Fix potential NULL deref in ensure_space.Robin Watts
Silly mistake in previous commit.
2012-02-13Create mudraw; mupdfdraw cloned and adapted to use fz_documentRobin Watts
All in one command line replacement for muxpsdraw and mupdfdraw.
2012-02-13Add locking around freetype calls.Robin Watts
We only open one instance of freetype per document. We therefore have to ensure that only 1 call to it takes place at a time. We introduce a lock for this purpose (FZ_LOCK_FREETYPE), and arrange to take/release it as required. We also update the font context so it is properly shared.
2012-02-13Remove STORE lock in favour of smarter use of ALLOC lock.Robin Watts
This simplifies other locking issues (notably freetype).
2012-02-13Remove arch_port.c from visual C solution/Android build.Robin Watts
File references escaped deletion in previous commit.
2012-02-11Purge unused and bit rotted fz_accelerate stuff, part 2.Tor Andersson
2012-02-11Purge unused and bit rotted fz_accelerate stuff.Tor Andersson
2012-02-11Build one library file instead of many smaller ones.Tor Andersson
2012-02-09Remove stray lock call.Robin Watts
I made a last minute change to make pdf_open_filter do the locking, and forgot to remove the call to lock from pdf_open_stream_with_offset. Fixed here. Thanks to Radu Lazar for pointing this out.
2012-02-09Update iOS code to latest changes.Tor Andersson
2012-02-09Update ios and Android projects with locking changes.Robin Watts
I forgot to update Android and iOS projects with the extra arg to fz_new_context. Fixed here.
2012-02-08Lock reworking.Robin Watts
This is a significant change to the use of locks in MuPDF. Previously, the user had the option of passing us lock/unlock functions for a single mutex as part of the allocation struct. Now we remove these entries from the allocation struct, and make a separate 'locks' struct. This enables people to use fz_alloc_default with locking. If multithreaded operation is required, then the user is required to create FZ_LOCK_MAX mutexes, which will be locked or unlocked by MuPDF calling the lock/unlock functions within the new fz_locks_context structure passed in at context creation. These mutexes are not required to be recursive (they may be, but MuPDF should never call them in this way). MuPDF avoids deadlocks by imposing a locking ordering on itself; a thread will never take lock n, if it already holds any lock i for which 0 <= i <= n. Currently, there are 4 locks used within MuPDF. Lock 0: The alloc lock; taken around all calls to user supplied (or default) allocation functions. Also taken around all accesses to the refs field of storable items. Lock 1: The store lock; taken whenever the store data structures (specifically the linked list pointers) are accessed. Lock 2: The file lock; taken whenever a thread is accessing the raw file. We use the debugging macros to insist that this is held whenever we do a file based seek or read. We also insist that this is never held when we resolve an indirect reference, as this can have the effect of moving the file pointer. Lock 3: The glyphcache lock; taken whenever a thread calls freetype, or accesses the glyphcache data structures. This introduces some complexities w.r.t type3 fonts. Locking can be hugely problematic, so to ease our minds as to the correctness of this code, we introduce some debugging macros. These compile away to nothing unless FITZ_DEBUG_LOCKING is defined. fz_assert_lock_held(ctx, lock) checks that we hold lock. fz_assert_lock_not_held(ctx, lock) checks that we do not hold lock. In addition fz_lock_debug_lock and fz_lock_debug_unlock are used on every fz_lock/fz_unlock to check the validity of the operation we are performing - in particular it checks that we do/do not already hold the lock we are trying to take/drop, and that by taking this lock we are not violating our defined locking order. The RESOLVE macro (used throughout the code to check whether we need to resolve an indirect reference) calls fz_assert_lock_not_held to ensure that we aren't about to resolve an indirect reference (and hence move the stream pointer) when the file is locked. In order to implement the file locking properly, pdf_open_stream (and friends) now lock the file as a side effect (because they fz_seek to the start of the stream). The lock is automatically dropped on an fz_close of such streams. Previously, the glyph cache was created in a context when it was first required; this presents problems as it can be shared between several contexts or not, depending on whether it is created before the contexts are cloned. We now always create it at startup, so it is always shared. This means that we need reference counting for the glyph caches. Added here. In fz_render_glyph, we take the glyph cache lock, and check to see whether the glyph is in the cache. If it is, we bump the refcount, drop the lock and returned the cached character. If it is not, we need to render the character. For freetype based fonts we keep the lock throughout the rendering process, thus ensuring that freetype is only called in a single threaded manner. For type3 fonts, however, we need to invoke the interpreter again to render the glyph streams. This can require reentrance to this routine. We therefore drop the glyph cache lock, call the interpreter to render us our pixmap, and take the lock again. This dropping and retaking of the lock introduces a possible race condition; 2 threads may try to render the same character at the same time. We therefore modify our hash table insert routines to behave differently if it comes to insert an entry only to find that an entry with the same key is already there. We spot this case; if we have just rendered a type3 glyph and when we try to insert it into the cache discover that someone has beaten us to it, we just discard our entry and use the cached one. Hopefully this will seldom be a problem in practise; to solve it properly would require greater complexity (probably involving spotting that another thread is already working on the desired rendering, and sleeping on a semaphore until it completes).
2012-02-07Updated Visual Studio Project; generated tweaks.Robin Watts
Rather than having a custom build step that generates the font and cmap "generated" files, have it as a separate project. This enables us to nuke the generated directory as part of the clean step, and to list the files in the solution explorer.
2012-02-07Update windows viewer to latest changes.Tor Andersson
2012-02-07Fix broken fz_clone_context; stupid typo.Robin Watts
When cloning a context, it's generally best to return your new context, rather than the one you cloned from.
2012-02-07Implement fz_open_document by hard coding the list of file types.Tor Andersson
2012-02-07Rename a few functions.Tor Andersson
2012-02-06Pass context to cmap and font descriptor functions.Tor Andersson
2012-02-06Fix 692841: Look at ConfigureNotify events while waiting for MapNotify.Tor Andersson
We used to discard all events until we got a MapNotify, but some window managers send the ConfigureNotify before the window is mapped.
2012-02-06Drop XPS links in the correct function.Tor Andersson
Prevents segfaults when revisiting pages and trying to access the link object that was freed too early.
2012-02-03Free current document page when closing pdf application.Sebastian Rasmussen
2012-02-03Fix NULL dereference when freeing fz_link objects.Tor Andersson
2012-02-03Be consistent about passing a fz_context in path/text/shade functions.Tor Andersson
2012-02-03Be consistent about passing a fz_context argument in pixmap functions.Tor Andersson
2012-02-03Pass context explicitly to hash table functions.Tor Andersson
2012-02-03Reference count fz_link objects.Tor Andersson
2012-02-03Remove extraneous blank lines.Tor Andersson
2012-02-03Use the new document interface in viewer.Tor Andersson
2012-02-03Add document interface.Tor Andersson
2012-02-03Make fz_malloc_struct return zeroed memory.Tor Andersson
2012-02-03Use image DPI in CBZ parser.Tor Andersson
2012-02-03Allow ZIP as extension for CBZ files.Tor Andersson
2012-02-02Support remote links in XPS documents.Robin Watts
Update xps path handling to cope with URLs. Fix premature freeing of links. Spot remote URLs and use appropriate link type.
2012-02-02Work on supporting links in xps documents.Robin Watts
Currently, this only works with local links. When running the page, check for NavigateUri entries; if found, and that page is not already marked as having resolved it's links, add a new link entry to doc->current_page links. When the page finishes running, mark the page as having resolved it's links. This avoids the links being generated multiple times. Update the mupdf viewer to use these links - but only AFTER the page has been run.
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-25 02:50:36 +0000