What is the proper way to check if a PDF is password protected? about uxmpdfkit HOT 4 CLOSED

You would be correct to assume the error should be propagating through. It looks like when we added in the ability to open a PDF from Data instead of just a file path this functionality broke. We moved all of the logic to a computed property so that calling it each time would pull from the latest variables that had been set. However, computed properties do not allow for throwing errors, so that is where the holdup is. A solution will be to move that logic to a function. However we will then have to either make the password, filePath and fileData variables read-only or will have to have the documentRef recompute when they are changed. Due to my schedule this change will be a couple of days, for the time being checking for nil is the best option, unfortunately that won't tell you if it was any of the other errors however. Sorry for the inconvenience!

from uxmpdfkit.

Hi @pushchris, thanks for responding! I'll use the nil-check for now, and update as soon as an update is available.

By the way, see also my pull request from a while ago: #8

from uxmpdfkit.

@rbresjer sorry for the delay, I have pushed code that moves opening of a PDF context to its own method. Would you mind pulling from the master branch and letting me know if it resolves the issue for you? If so I'll go ahead and publish a new version. Thanks

from uxmpdfkit.

@pushchris Hi Chris, thanks, I just tested and it works!

from uxmpdfkit.