Hollywood forum

I haven't looked at that yet. Might be possible by adding some custom code using the professional edition of APK Compiler but of course this requires some knowledge about Android internals.

I don't think that this is possible by fair means.

Okay, I've adapted this now to be more consistent. pdf.GetLastError() will return 0 on success now.

After examining the PDF I can confirm that it really has the coordinates in the unusual order. But according to the Adobe PDF specification, this is completely legit: Rectangles are used to describe locations on a page and bounding boxes for a variety of objects. A rectangle shall be written as an a...

Ok, so this is because the PDF in question defines a crop box and the coordinates returned by pdf.GetPageLinks() are relative to the crop box. I've now added two new functions to get a page's crop box and media box: - New: Added pdf.GetMediaBox() to get a page's media box and pdf.GetCropBox() to get...

Hmm, well, actually the behaviour on MorphOS is the one that should be the normal one. You must only call pdf.GetLastError() if pdf.OpenDocument() actually failed so I'll have to examine why the error state is reset on Windows because that normally shouldn't happen, although it might be quite common...

I'll see what I can do.

Ok, I've just checked the code and indeed mouse support needs Android 5.0 now because it supports left, right, and middle mouse buttons now. So I'm afraid it won't work with KitKat...

Yes, that's normal. PDF uses an origin in the bottom-left corner instead of the top-left corner (as described here). I don't know, though, what's the deal with that PDF you mentioned which seems to have the coordinates in canonical order?! Can you provide that one so I can take a look?