| Age | Commit message (Collapse) | Author |
|---|
|
The tiling in x and y is needed to ensure that we can print at high
resolutions with devices that have smaller bit map sizes (e.g. the surface).
Banding only in the y dimension like we often do is not sufficient.
Also fix an open with file association bug that must of occurred with the
transition to 8.1
And update WinRT solution for recent changes in mupdf code. This includes
the addition of a few new files and the document type registration.
|
|
issues with surface thumb rendering.
Also, make updates for changes made to font names and 3rd party file structures.
|
|
|
|
After much research it was determined that use of the DirectX 2D methods is the proper way
to add printing support to a Windows 8 application. This enables the pages to be rendered
as they are requested by the print thread. This occurs for both the print preview screen
as well as the print to the output device.
|
|
+/- 2. Thanks to Robin for catching this.
|
|
This uses the xaml printing methods. It is likely that I need to go do a DirectX approach since the xaml
printing method could run into memory problems as it seems the architecture requires all the pages to
be rendered prior to the print job even starting. Currently checking on this with a contact at MS.
I wanted to get this code in place now since it is working and it has the needed framework for much of
what we want. A change to DirectX requires a changes in the solution file that may be complicated and so it
makes sense to do a split here with respect to providing printing support.
|
|
Also fix issue that occurs in Windows 8.1 with an unhandled exception
if a mouse scroll occurs before a document is even opened.
Fix issue with keyboard based update of page slider.
|
|
Proper use of mutex lock in areas where we multiple threads can
not be accessing the document or page level objects at the same
time. With this fix, multiple threads can be rendering different
display lists at the same time.
Also fix for use of page selection scroll bar so that it does not
render the page until the user lifts off the bar. This is the
same as the Android app and avoids smaller devices getting overloaded
if you do rapid scrolling in a document.
|
|
|
|
15b9cdd84caf784abeb911ca7aaf1d317d201e88
|
|
|
|
undertaken
|
|
|
|
|
|
|
