Christiaan,
Not being familiar with the structure of the code, this didn't seem odd
from the start to me, but certainly you're the expert here! I'm just
reporting what I see...
To me, it's promising that it appears to correct after scrolling far enough
to force a refresh (without relaunching app). I'm thinking that
invalidating the display region might be a workaround, even if it flickers.
I'm installing the High Sierra Supplemental Update as we speak; there is no
indication that PDFKit fixes are in there, but I'll re-run the experiments
and report back to the list with my results.
Thanks for providing your insight!
-Richard.
On Thu, Oct 5, 2017 at 3:14 AM, Christiaan Hofman <[email protected]>
wrote:
> Yes, this is essentially how I had understood it. It just does not make
> any sense to me, because programmatically the addition of old highlights
> when opening the file is completely equivalent to adding a new highlight
> later on. These are the same kind of objects added with the same exact
> code. The only difference is *when* they're added.
>
> Christiaan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Skim-app-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/skim-app-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Skim-app-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/skim-app-users
