v. 1.4.29
os High Sierra Beta
colors have all become 100% opacity.
trying to make a default yellow highlight results in a yellow line obscuring the text,
instead of the expected 30% opacity highlight.
Correcting with the opacity slider is forgotten when skim is reopened.
Clicking another one of the colored pencils or crayons to change to say,
light blue highlight -> this color is also 100% opacity.
This is a bug in 10.13. We simply set the color, Apple's code in PDFKit
draws the note. We don't influence that, and in fact cannot. You should
report this to Apple. Only they can, and should, fix this.
I may sound like a PITA, but would that not be much more adequate to raise this case from the point of view from Christiaan? After all, this lets all users of Skim (again, see last year) very much hanging out there to dry, since all annotations / highlights are now unusable.
My point is that we cannot fix this. Apple us the only one that can. And
the more people that report this problem, the more chance Apple will do
something about it. I did already report it, but that's just one report.
Sure, and I've of course done a bug report.
I created a bug report. Hoping PDFKit gets fixed soon. I was pretty dependent on Skim. All my PDFs are wrapped in bundles and I have a year's worth of highlights on them.
Update: Installed latest update, no fix. Skim is practically unusable right now.
By chance, I found a way that corrected the opacity of my highlights.
Upon opening a PDF that had been annotated with Skim, all I did was show the notes pane, and double click on any highlight note, and it corrected the opacity of all of the highlights.
I hope this works for some others experiencing this problem.
Can't confirm. Adding a note, double clicking around on other notes, note stays on 100%. Also changing the opacity down from 100% to something else, and again double clicking around, doesn'thelp.
I got mixed results, but mostly it didn't work. Opening the notes pain the first time fixed one highlight. subsequent highlights were broken. Closing and reopening the document broke all of the highlights again. See attached screenshot.
Last edit: Berry Green 2017-10-17
FWIW, new highlights fail with 100% opacity. old highlights display with correct opacity.
Update from here, Apple closed those bug reports saying they are duplicates, and did not reveal duplicates of which. It really sucks since it makes Skim entirely unusable on High Sierra for annotating. I used to read tons of scientifc articles with Skim, and now it seems it's over.
Oh yeah, to answer my own question, my old fix that I've described here:
https://github.com/mnott/skimenabler
solves this problem. So essentially, I open a command line, and then do this:
cd ~/Desktop
git clone https://github.com/mnott/skimenabler
cd skimenabler
./install.sh
When starting Skim again, highlighting seems to work just fine.
I had forgotten about that solution which I created a while ago when having other problems with Skim - sometimes, we do need to remember drinking our own koolaid...
HTH,
M
Apple closed my bug report as well for the same reason.
Question: If I use your method (downloading and installing the file from github), will it mess with any system files? Can it be undone easily? If so, how? Thank you.
It dies mess with the system. Though it probably won't affect other parts
and other apps. But it will have other side effects, including opening up
other bugs in Skim. We have workarounds for bugs in this alternative PDFKit
version that won't be effected because we don't know it's there. And it is
not compatible with the rest of the system.
Note that this bug really is not this serious, certainly not worth messing
with your system. The opaque highlights do go away by themselves after
changing some view settings or location changes in my experience.It is
annoying, I know, but there have been much more serious bugs in PDFKit,
including in the one that would be used as a "fix".
Thanks for the heads up. Also, if you're able to provide instructions on how to get the opaque highlights to go away, that would be cool. It's important that I am able to use the highlighter for notes.
I don't understand why other programs, like Adobe, don't have this issue. I guess I'm sticking with Adobe Acrobat until something changes, but I'm monitoring this thread.
The big is in Apple's PDFKit, which is not used by Adobe.
You can get rid of it by getting the view to redraw, by changing things.
For instance change to single page an move pages, or mice by a lot of
pages, eg to the end of the document temporarily. Sorry, Apple has also
made it impossible to tell the view to redraw in High Sierra.
Oh wow, that worked. Thank you.
I am using High Sierra, just FYI. Switching between dual and single pages worked, although its just a temporary fix, not permanant.
So if I select text and highlight it, the highlight is 100% opaque.
If I rotate it 4 times, then the highlight transparency is correct.
Rotating the page once is not enough.
Again, if I use Skim to display my old PDFs with highlights already
selected, they display correctly.
On Sat, Nov 11, 2017 at 11:55 AM, Berry Green berrygreen@users.sf.net
wrote:
--
Ite Ursi
Related
Bugs:
#1198Well, my version of the script does not mess with the system files. It just patches Skim. And FWIW, I don't consider this a "not this serious" bug, since it makes Skim mostly unusable: I don't see why I should be messing around with rotating my pages all the time.
Anyway, if you look at the script, you see that it defaults to not needing root, not needing sip, and hence not patching anything in the system files. It just patches Skim itself, to point to a version of PDFKit which it brings along; and hence it has no influence whatsoever on the rest of the system.
Works well on my system.... ¯_(ツ)_/¯
Hi guys! This PDFKit bug just completely disrupted my beloved Zotero + Skim workflow. How should we file a bug report to Apple? What should we write exaclty and where? Thanks a ton. Cheers!
Last edit: spacefolder 2017-11-11
Bugs can be filed at bugreport.apple.com. Say that new highlight
annotations in PDFKit are initially opaque and blocking the text.
Thanks Chris, I'll do that!