In google-chrome-stable on Linux, I tried to highlight and then underline. It seems the underline erased the highlight. But when I load the pdf in paperpile, both were present (which is what I want).
In google-chrome-beta on Linux, the connection to google-drive does not work.
In both -stable and -beta, if a pdf has been viewed from paperpile, then annotated in metapdf, annotation will not show in paperpile. I was not able to find a refresh pdf function in paperpile.
The automatic re-syncing back to Paperpile is not part of the current beta. You can trigger a re-sync though by starring or unstarring a paper. That will re-download the file from Google drive to the local cache if it has changed.
If you say âconnection to google-driveâ does not work. Does this mean if you click âOpen from Driveâ the open dialog does not show?
If thatâs the case can you click âF12â and send us the output of the debug console.
I have not been able to reproduce (I tried with beta and stable).
I just tried google-chrome-beta on my office computer and the âConnect to driveâ function works. I think I have the same setup at home but Iâll check again when I get back.
There was an error!
The API developer key is invalid.
GET https://app.metapdf.com/resources/css/app.css.map 404 (Not Found)
app.min.js?v=24:1033 Loaded Google Picker API
rpc.js?c=1&container=onepick:449 Failed to execute âpostMessageâ on âDOMWindowâ: The target origin provided (âhttps://docs.google.comâ) does not match the recipient windowâs origin (âhttps://app.metapdf.comâ).
picker?protocol=gadgets&origin=https%3A%2F%2Fapp.metapdf.com&navHidden=true&multiselectEnabled=trueâŚ:3 Uncaught ReferenceError: init is not defined
clobbercookie.js:19 clobbering cookies for
Location {replace: function, assign: function, ancestorOrigins: DOMStringList, origin: âhttps://docs.google.comâ, hash: âââŚ}
.
When opening a new file, shouldnât I be able to open a file that I just downloaded by dragging that file from the âdownload barâ at the bottom of Google Chrome to the âDRAG FILE HEREâ box in metapdf? Doesnât seem to work.
Thanks. Do you have the PrivacyBadger or any other Adblocker or Privacy extension installed? If so, can you try disabling them and see if it solves the problem?
Itâs not immediately obvious how to turn highlighting off so that I can simply copy text. The most logical thing I could find was to click on the triangle portion of the highlight button at the top, and then click on the color that was selected to turn it off. This, of course, didnât work. It didnât occur to me for quite a while to click on the pencil icon itself. Perhaps there is a way to make that more apparent to users?
Iâve sent you the papers
Edit: this forum has a bug? I currently edited this message with 4 numbers, only 2 apper (try to edit this message and youâll see 4 different items listed)
Few more suggestions/problems:
Be able to hide notes inside text. If I have a paragraph with 15 notes, the bubbles on the right side are overwhelming. If there are too many of them. it creates a white (new) page after the commented page, which is not useful.
Macâs trackpad (rMBP mid-2012) is too sensitive in terms of zooming in/out the paper (by pinching)
The papers I sent you also have problems with strikethrough and underline
Annotating/commenting next to a floating picture (side of a text), destroys the picture
Same happens with a new post, is there a max allowed characters per post?
4. Annotating/commenting next to a floating picture (side of a text), destroys the picture
5. Scrolling isnât smooth when there are pictures in proceeding pages - at least not in Chrome for Mac. Preview/Chromâs PDF reader is much smoother than metaPDF (not critical, but it can create an issue when there are zillion images on proceeding pages and the PDF is pretty heavy because of that.
6. Zooming in/out creates a disturbance on the font:
Thanks for reporting these issues. I have not been able to reproduce them on my computer. Do you see some of these issues also when you use the regular PDF.js viewer?
There can be 32000 characters per post. Not sure why you have trouble posting. Settings are complex for this forum. Iâm still learning.
As for the bugs. Andreas will have a look at it. More generally, itâs important that metapdf can never be as fast as a ânativeâ PDF reader like the Chrome reader or Mac Preview. MetaPDF is based on pdf.js which is the default viewer in Firefox. So it inherits all the limitations. However, itâs an active project and will become more stable and faster with time.