Unable to print all pages of large documents

GroupDocs.Viewer Product Family
,
21

@vladimir.litvinchik Great, Thank you!

22

@sachinerande

You’re welcome!

23

@sachinerande

There are two updates in the latest version of GroupDocs.Viewer.UI 8.0.2

Print

The feature where images are printed instead of PDF in image mode was moved from version 6.0.x to 8.0.x.

File name

This feature was fixed and now hides file name from top bar and thumbnails pane.

Also, you can set the file name using your implementation of IFileNameResover interface and registering a service:

builder.Services.AddTransient<IFileNameResolver, MyFileNameResolver>();

public class MyFileNameResolver : IFileNameResolver
{
    public Task<string> ResolveFileNameAsync(string file)
    {
        return Task.FromResult($"Custom file name for {file}");
    }
}

custom-file-name.jpg1269×972 75.9 KB

To get the changes update you GroupDocs.Viewer.UI and GroupDocs.Viewer.UI.* packages to the latest 8.0.2 version.

The complete list of changes can be found in the release notes

Please let us know if you have any questions.

24

Hi @vladimir.litvinchik Thanks for updating. I am noticing following problems with the upgrade.
We have PreloadPageCount set to 300
Viewing document of 98 pages ( < 300)

Issues observed -

  • When loaded pdf in the viewer, it renders all pages, sometimes few are missing either in thumbnail or it’s actual page. (need to scroll or click on print button to load them, and sometimes it doesn’t load altogether.)
    Here is the screenshot for “sample_pdf_printing_problem_1.pdf” that was shared with this ticket.
    image.png (44.1 KB)

  • Simple scroll operation sometimes shows scrolling 5-6 pages at a time as that appears in page number field. (may be double check the page no fix is correctly applied)

  • Clicking print button - following loading pages popup always loads clicking on print button, even though pages are already rendered, and it takes a while to finish. (may be making calls to backend again)
    image.png (6.0 KB)

25

@sachinerande

Thank you for reporting this issues, we’ll analyze them and update you. The issue ID for reference is VIEWERNET-5240.