| Age | Commit message (Collapse) | Author |
|---|
|
Since the removal of the begin_page device function, structured
text extraction has been unable to correctly establish the
mediabox for extracted pages.
Update the fz_new_stext_page call to take this mediabox
information. This is an API change, but hopefully most people
are calling fz_new_stext_page_from_page or
fz_new_stext_page_from_display_list which are updated here to
cope.
Update all the apps/tools to behave properly.
|
|
|
|
Uses the more modern/concise syntax that arrived in Xcode 4.4
|
|
|
|
|
|
We're a subclass of UIViewController, so must call one of UIViewController's
designated initialisers.
|
|
What is effectively our external API on iOS would be expected to use
NSString rather than char *.
|
|
We shouldn't output any debug in default release build.
|
|
|
|
|
|
shown.
|
|
Android viewer project.
|
|
Also remove redundant assignments.
Fixes http://bugs.ghostscript.com/show_bug.cgi?id=695968
|
|
|
|
MuPrintPageRenderer.h:2:9: error: 'MuDocRef.h' file not found with <angled> include; use "quotes" instead
MuPrintPageRenderer.m:35:16: warning: if statement has empty body [-Wempty-body]
MuPrintPageRenderer.m:35:16: note: put the semicolon on a separate line to silence this warning
|
|
In preparation of adding pdf_write_document that writes a document
to a fz_output stream.
|
|
- added four zlib files to Makethird that contain functions needed
by the new version.
- added -Wno-implicit-function-declaration so these new files, which
contain some implicit declarations, would build for iOS
- added a section to Info.plist that holds the new API key, with an
invalid value that the release build script will fill in.
- changes to MuAppDelegate for the new version.
<log></log>
|
|
Less risk of confusion with the text type used in the device interface.
|
|
arrays
The list box and combo box can have values that are 2-element arrays. The first element
is the "export" value and the second element is the value that should be shown
in the list box UI. This fix ensures that we get the proper value to show in the UI.
Also, it adds the option to get the export values. These are needed if you wish to
update the field dictionary's V (value) entry, which is the currently selected values(s).
This fix works well with gsview. The other viewers will now display the proper content
in their UI, (unlike before this fix) but may need a bit more work to ensure that the
proper V (value) is updated with changes in the selections. In addition, we add
selection rectangles to the selected list box items.
|
|
|
|
popover presentations need to be told which button to emerge from
|
|
|
|
|
|
|
|
|
|
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_*.
|
|
|
|
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.
|
|
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.
|
|
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().
|
|
|
|
|
|
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.
|
|
|
|
|
