Quote:
Originally Posted by DiapDealer
Not to say that the same thing won't happen in the official latest version of Sigil, but until it's verified that it does ... apples and oranges.
|
All I know is what happens on my PC. I'd be rather surprised if this was something that depended on the version of Qt.
Quote:
Originally Posted by DiapDealer
Besides ... " Preview sometimes doesn't scroll" is hardly relevant to the portion of my post he quoted where I talked about how Preview and Book View both render the same code the same (because they use the same rendering engine).  |
I didn't say they don't render the same, it's how they react.
But actually, now I know that it syncs up with the cursor, and not the visible code which is what I expected, it's more explicable, though still rather frustrating, for me at least.
When I am editing in codeview, my cursor is usually in the para I'm editing and want to preview so the Bookview will sync (and so will the preview).
But if I'm scrolling through the code (using mousewheel or scrollbar), the preview does not move, and if I switch over to it, it jumps back to the start; if I click in it it pulls the code page back to the start and I lose my position there too. So I blamed the preview, when it actually affects both "views".
Now I know it's all about the cursor, a workaround is always click in the text to put the cursor where you want to preview. If I use pageup/down to jump the cursor, it does sync, but not smoothly, a lag of a second. So here bookview is preferable: I can scroll through it smoothly, put the cursor in the text, F2 and be in the code. Disclaimer: maybe this is due to my own setup, YMMV.
Not that my preference matters, but I think it would be more intuitive if the preview display synced with the visible code screen, not wherever the cursor is, which is usually at the top of the file if you scrolled without clicking in the page.