-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong positioning of the search marks #85
Comments
+1 could be nice to get sorted out. |
I have almost fixed the issue now, so the general solution works. Will commit and push today. |
I will commit it as soon as all the bugs are fixed! Are working on it atm! :) |
I will commit the fixes soon. I also implemented support for newline word searching, so we can mark search words spanning more than one line. When I commit, you can fork it and implement your fixes. |
..... 2015-06-12 16:18 GMT+07:00 TryMyBest [email protected]:
|
The commit is up. Now remember that there might be more bugs. If so, post them. I am still working on making it a lot better. |
Yes just saw that. Though that is only in the test project. It does work when you give it the correct page size. The way Kitten sets up a page, is pretty weird. It works fine otherwise: I will see if I can fix it in Kitten. |
What you need to pass to the convertPDFRectToViewRect method is the frame of the userSpace PDF page aka. the visible pdf page you are viewing. Anything else will fail. |
Still mark on the wrong position~ http://www.takming.edu.tw/study/upload/filedownload150318163116.pdf |
Hi KurtCode
I have the library with different PDF files, and it does often place the search marks wrong. In my fork, there is a PDF file called amazon-dynamo-sosp2007.pdf. Searching for the string "re" will show you that the position of the marks a sometimes calculated wrong, since they are misplaced. The same goes for the string "in" and probably others.
Is this something you might be able to fix?
Have a great day
Regards,
Kenneth
The text was updated successfully, but these errors were encountered: