qpdfview team mailing list archive

[Adam Reichold <adamreichold@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On 15.06.2012 19:09, Andi Șerbănescu wrote:
>> The application-specific buttons are application specific and 
>> therefore can not use the icon theme. (I think this is page 
>> layout and scale mode.) Again, this is as intended.
> 
> But there are icons for those things: zoom-original, zoom-in, 
> zoom-out, zoom-fit-best. Plus the non-standard ones. I'll compile
> a list.

Yes, there some icons. And we do use zoom-in and zoom-out. But for the
sake of consistency, zoom-fit-best and zoom-original are not used.

Hence the list of actions with application-specific icons is:
onePage,twoPages,oneColumn,twoColumns,fitToPage,fitToPageWidth,doNotScale

Those icons are shipped with qpdfview in /usr/share/qpdfview as SVG
files and are always loaded directly.

Everything else should use the installed theme icons. If not,
something is wrong. Since this works at least for me and some people I
know on different distributions, a configuration problem does not seem
unlikely.

>> What would be unintended is if the non-default buttons would 
>> display text even though there is an icon theme present. But 
>> since this is known to work on other platforms, I suspect a Qt 
>> configuration problem.
> 
> Oh, boy, here we go again :)
> 
>> I checked mupdf as backend and wrote some proof of concept. But 
>> it is rather unstable compared to Poppler which seems better 
>> supported and easier to develop with.
> 
> So chances are we won't be seeing it…

Well, I went pretty far in implementing it and did not really find a
benefit from the user's point of view. And for example, it did not
even load large files like the PGF manual and I was able to crash the
supplied multi-threaded example program using PDF files that Poppler
rendered just fine.

Maybe in the future, I definitely have this in the back of my mind.
But very probably not on short notice.

>> I was wrong. The problem was/is different. I unintendedly scaled 
>> the pages when drawing them. So these distortions should be
>> gone. But the infamous "one pixel too small" problem returns. But
>> this seems rather preferable in this case... Trunk should have
>> the fix...
> 
> Did it ever go away? :) But what about ditching the (physical) page
> metaphor completely, along with the borders and the grey 
> background, and use the full extent of the ‘workspace’ instead?
> See zathura for an example; acroread also does this optionally.

Interesting idea. Will think about that. Probably not for 0.3.

>> Again, a test file may be helpful. Does it happen with the file 
>> you sent earlier?
> 
> Happens with everything. I don't think it's the documents' fault.

If so, the problem will be hard to pinpoint without you running a
debugger. At least this tells me to have a look at the refresh-cycle
again but random crashes are rather hard to find.

>> I think the result of that discussion was: Left/right for 
>> previous/next page and PgUp/PgDn and Sp/Bksp for scrolling one 
>> screen at a time. Works exactly like that for me.
> 
> But is is supposed to work this way only for continuous? Because
> it only works that way for me. In non-continuous, everything
> simply skips pages.

No it works in both modes. But maybe this was unexpected for you: If
the next screen lies partially on the next page, the program would
skip to the next page. I just commited a change that will make an
"extra stop" for the last partial screen before skipping to the next page.

Other than that it is supposed to work in paged mode.

> Andi
> 

Regards, Adam.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP25h7AAoJEPSSjE3STU34Vj4H/2+WVLHjYk8lCu1peosG7/zJ
RYpOOuY7Q+Dloui54+pHhyetl/reCy+JgIk8LfqFq283KnWDNTXMInW19R23nQFt
VE8D2X4WK597LnvDdadqc+f573vmdkf28mCF2T5lFXSom6Er7cg2PSKh0BD1rGjI
UCIO5OoAr6fz+l7WZnQ0X69tyhmyjsY2OUuhTP1pOf9fyZWWH5kxmUEivlMl64B9
xJKxdkDEGLdWxCL4S0cYzF0JjKJNfQlUv6HdoFTgiMNlJkb6D/md8mSp48kkTcMj
gIzuishjInmKqGliDKw0DklQQhKjSUiJrRCCUjVHBYH8ozxTduZ16yJTS/5aebI=
=cTsj
-----END PGP SIGNATURE-----