ngx-extended-pdf-viewer | blown PDF viewer | Document Editor library
kandi X-RAY | ngx-extended-pdf-viewer Summary
kandi X-RAY | ngx-extended-pdf-viewer Summary
A full-blown PDF viewer for Angular 12, 13, 14, 15, and beyond
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ngx-extended-pdf-viewer
ngx-extended-pdf-viewer Key Features
ngx-extended-pdf-viewer Examples and Code Snippets
Community Discussions
Trending Discussions on ngx-extended-pdf-viewer
QUESTION
I want to implement Ngx-extended-pdf-viewer default (horizontal) scroll but I have implemented below code but not working
https://pdfviewer.net/extended-pdf-viewer/display-options
Version: "ngx-extended-pdf-viewer": "^7.3.2",
...ANSWER
Answered 2021-Sep-27 at 18:28Please clone and run this repository: https://github.com/stephanrauh/ngx-extended-pdf-viewer-issues/tree/main/stackoverflow-sanjay. It's my attempt at reproducing your issue. Only it works like charm. So my suggestion is you get my reproducer up and running (just to see if there's a general problem). After that, compare my reproducer to your project. That should help to to find the problem quickly.
If it doesn't, please open a ticket at https://github.com/stephanrauh/ngx-extended-pdf-viewer/issues and send me a reproducer.
BTW, you don't need the setter and the getter. That was necessary for my demo, but in your case, a global variable does the trick just as well. The same applies to using NgZone
. I needed it in my demo, you in your case, horizontal scroll is the default and it will never change, so you don't need NgZone
.
QUESTION
In my Angular app, I have installed via npm
the ngx-extended-pdf-viewer
so that I can display the content of pdf files.
As per instructions, I have included the following in my angular.json
file:
ANSWER
Answered 2021-Sep-10 at 19:02Nowadays, installing ngx-extended-pdf-viewer has become a lot simpler. You don't need the scripts
section. The pdf*.js
files are loaded automatically. Your advantage: you benefit from lazy loading, and your PDF viewer is a lot faster.
Technical deep dive: Many users of my library had problems with caching. When I publish a new version, they'd still use the old version of pdf.js. To solve this problem, I've added the version number to the file names. That, in turn, causes your error message.
Not including the JavaScript files has two other advantages. First, the pdf*.js files are only loaded when needed. So your initial bundle is a lot smaller, and the application loads faster. Second, pdf.worker.js
is executed in a worker thread. For large PDF files that's a factor ten performance boost.
QUESTION
I have created an webapplication with Angular 11. Now, the customer will run it with IE11 (for showing a webpage on a big TV-Screen which still exists and have an integrated IE11-Browser)
for this,, I have set up all this
https://angular.io/guide/deployment#local-development-in-older-browsers
and uncommented the lines in polyfills.ts (and run the npm-commands):
...ANSWER
Answered 2021-Aug-27 at 13:24You have to update your tsconfig.json
and set target to es5
:
QUESTION
I'm trying to use ngx-extended-pdf-viewer
in an Angular project that uses amd.min.js
as an dependency. If I remove amd as an dependency it's working fine. But sadly I can't remove it as, a lot of other things are dependent on it.
Here's the reproducible html.
...ANSWER
Answered 2021-May-25 at 12:58Load all three pdf modules before amd.
QUESTION
I was using Angular 11 with Angular Material 11. I group multiple angular project into one. All of those projects are working. Now, we are using Angular 9 with Angular Material 9.
We only change the structure, but the code is the same (the app.module.ts is also the same). It's just that package are manage by the main project and not my own only.
But there is a problem with this fusion. It's with the dialog which was :
And know is :
which is a little bit different.
Parts of my app.module.ts :
...ANSWER
Answered 2021-Jan-15 at 08:22I found the problem.
The CSS file was buggy, and after a Material reinstall and importation of angular material's css, it works fine.
QUESTION
I am using the latest stable version of ngx-extended-pdf-viewer (4.1.2) and Angular 9.1. Everything work's great but after the application is built certain PDF-files don't show any text. It turns out that the reason was that the request for the .bcmap files fails.
Instead of requesting the bcmap files from: my-application/en/assets/cmaps/Adobe-CNS1-UCS2.bcmap
... the bcmap files are actually requested from: my-application/assets/cmaps/Adobe-CNS1-UCS2.bcmap
I don't understand that behaviour since the pdf.worker.min.js is correctly requested from my-application/en/assets/.
My angular.json assets setting looks like this:
...ANSWER
Answered 2020-Oct-01 at 19:12You've found a bug. Either you update to version 5.0.1 (which fixes the bug). Or you use the default options for a workaround:
QUESTION
I am using the ngx-extended-pdf-viewer and I want to add a div on each page.. It works as expected.. my dom looks like this: (the div with the class="con" was added by me)
but if I am going to push the zoom button - the added div disappears..
My Code looks like this:
...ANSWER
Answered 2020-Aug-03 at 19:27That's simply not a use-case I had in mind when I created ngx-extended-pdf-viewer
. :) However, I assume you can use the (pageRendered)
event to achieve your goal. I'm puzzled zooming redraws that HTML code, too. Maybe that's a side-effect of (pageRendered)
. If not, you'll also want to catch the (zoomChange)
event to check if you need to add the div
again.
QUESTION
I am currently working with ngx-extended-pdf-viewer with Angular8+ to render a PDF, it doesn't work. And I keep getting the runtime error "Can't bind to 'src' since it isn't a known property of 'pdf-viewer'".
Does anyone know why this is?
Here is my HTML:
...ANSWER
Answered 2020-Apr-15 at 18:56Try [(src)]="pdfSrc"
It's a two-way binding attribute.
QUESTION
I'm pretty new to Angular, and can't seem to work out how to organize my code properly.
I have a page called BudgetComponent, which belongs to BudgetModule. BudgetComponent displays an accordion list of AccordionItemComponents. I want to use these Accordion Components elsewhere, which is why they're their own component class.
The AccordionItemComponent has an img that when clicked opens a MatDialogue. The MatDialogue contains a reference to an imported module ngx-extended-pdf-viewer (from an online library).
I have created an AccordionItemModule (which I'm not is necessary/correct) to house the corresponding component, but then I'm not sure how to make instances of this in my ngFor.
I'm really struggling to figure out which components should belong to which modules, and how to make all of this work, so that another component (with it's own module like Budget (ie Schedule)), can also reference AccordionItems. I'm not sure if I'm missing necessary routing or export logic, or what...
I have included a diagram to make sure the intended use is clear.
Thanks for any help.
...ANSWER
Answered 2020-Apr-12 at 06:28You are going in the right direction here.
Firstly, export AccordionItemComponent
like this exports: [AccordionItemComponent]
in your AccordionItemModule
class.
Secondly, add AccordionItemModule
to imports
in your BudgetModule
and ScheduleModule
class since you wish to use AccordionItemComponent
component in there.
Thirdly, pass data from Budget
and Schedule
component to the Accordion
component by adding it in the html file as follows:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install ngx-extended-pdf-viewer
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page