| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
popover presentations need to be told which button to emerge from
|
|
|
|
|
|
|
|
This silences this warning:
thirdparty/jbig2dec/jbig2_text.c:899:73: warning: for loop has empty body [-Wempty-body]
for (SBSYMCODELEN = 0; (1 << SBSYMCODELEN) < SBNUMSYMS; SBSYMCODELEN++);
^
thirdparty/jbig2dec/jbig2_text.c:899:73: note: put the semicolon on a separate line to silence this warning
|
|
There are a fair number of warnings about unused functions, mostly in
third-party modules, and we would like the build to be warning free.
We need to change the main Makefile, as -Wall is currently added in
Makerules, and we need our -Wno-unused-function in XCFLAGS to be
after -Wall on the command line for it to have any effect.
|
|
|
|
Rename fz_close to fz_drop_stream.
Rename fz_close_archive to fz_drop_archive.
Rename fz_close_output to fz_drop_output.
Rename fz_free_* to fz_drop_*.
Rename pdf_free_* to pdf_drop_*.
Rename xps_free_* to xps_drop_*.
|
|
|
|
These are now generated by Xcode at build time from the asset catalogue,
and the CFBundleIconFiles we had here was upsetting the app store validator.
|
|
All that is necessary is to add a launch xib.
|
|
Still more warnings left.
|
|
unused variables / functions / potential uninitialised variable usage
|
|
|
|
|
|
In MuDocRef initialise. it spotted cases where self could be released
twice after a failure.
|
|
|
|
scrollViewDidEndZooming takes a CGFloat.
|
|
Spotted by xcode6 analyser
|
|
These are private details that, since changes in Xcode, no longer need to
be exposed in the headers.
|
|
|
|
The background colour of the MuDocumentController's root view wasn't set,
so the MuLibraryController was showing through until it had been removed
from the screen.
Fix by setting the background colour to gray - the same colour as the
window.
|
|
A bug in UIKit means our 'scrollViewDidScroll' method is called during
screen rotation. This ended up corrupting our current page number because
the width of the screen had changed at this point, but the pages hadn't
yet been resized/repositioned (I assume).
The workaround is to ignore calls to scrollViewDidScroll during rotation.
|
|
This debug output was listing the names of all the files to the iOS console
every 3 seconds. Remove it.
|
|
Used by the Testflight build.
The post-archive step requires nastiness to pass the result of the script
back to the caller via a temporary file. The reason for this is that a bug
in Xcode means that failures from post-archive steps do not get propagated
back to the user who called xcodebuild archive.
Also, update the postbuild script to explicitly invoke bash (so we can
avoid assuming /bin/sh is bash, and to avoid problems where executable
permissions aren't set properly).
|
|
It is recommended that you delete any personal schemes that have the same
name as the shared ones, for example by cleaning your git tree with:
cd platform/ios/MuPDF.xcodeproj && git clean -X -f -d
(this will wipe out any .gitignore'd files in your tree - so be careful.
Make sure you use an uppercase -X option; the lowercase version will wipe
non-ignored files!).
|
|
Add hooks to allow us to pass in the Crashlytics SDK location and the
API key from the command line. The SDK and API key will be held in a
separate private repository.
Should have no effect on regular builds.
|
|
Speeds up compilation, and means we can avoid having to list all the system
frameworks (so I've deleted them).
|
|
Previously on iOS 7, bar buttons didn't change visually when disabled.
Also improves the look and feel - the buttons are now tinted in the
highlighted state rather than showing a grey background. On iOS 7, the
iPhone/iPad buttons style match.
Tested on iOS 6 iPad/iPod and iOS 7 iPad/iPod.
|
|
|
|
The features do not work in reflow mode - Android already disables them.
|
|
Remember to release self, if we're returning nil from the initialiser.
Also, there is no need for fz_var(doc), because doc is an ivar and
effectively equivalent to 'self->doc'.
|
|
Handle exceptions from fz_open_document().
|
|
Use the UTI 'public.cbz-archive' instead of the more generic
'public.zip-archive'. It's likely another app (or the OS) has an
Exported UTI for 'public.zip-archive' which would take precedence over
our Imported UTI and not have a 'cbz' extension.
It's not entirely clear what the correct UTI to use for CBZs is (there
are a few), but public.cbz-archive seems to be most likely candidate.
Remove the 'zip' extension, as we probably don't want to load arbitrary
zip files.
Add mimetypes for all completeness, and separate OXPS from XPS as it has
a different mimetype.
|
|
|
|
|
|
|
|
Correct an off-by-one error in the file deletion code.
|
|
Fixes bug #694711. As far as I could see, opening an XPS worked fine, the
first time. However, if the same file was opened a second time, then it
should have been saved with a number, e.g. foo(1).xps. However, the period
was ommitted, so the file wasn't recognised as an XPS.
This presumably wasn't an issue for PDF files, as PDF format is assumed
by default (I am guessing).
|
|
Most were pretty harmless, and were addressed by renaming functions to match the Core
Foundation naming conventions, but there was one actual memory leak, and some potential
uses of uninitialised data.
|
|
If an iOS app uses too much memory, the OS asks it to free up some space.
If it doesn't do so in a timely manner, it will get a second warning before
being killed by the OS.
In other platforms, where malloc() return NULL in OOM, the store scavenger
releases memory when mallocs fail. In iOS, mallocs usually never return NULL
because the app is killed before this can happen. Therefore, we need to
initiate a scavenge from the low memory notification instead.
We evict the store to 50% of its current size when a memory warning occurs
when it is in the foreground, and 0% when a memory warning occurs whilst
it is in the background. Having said this, I didn't manage to get a background
warning to occur, presumably because we don't request background execution
Therefore, I think in practice the OS just kills the process. However, this
will be useful if we ever add background execution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
