Version: 1.3 (using KDE 3.4.0 Level "b" , SUSE 9.3) Compiler: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) OS: Linux (i686) release 2.6.11.4-21.7-default In earlier versions it was possible to zoom and position the viewed page in a way that the upper and lower marginals are outside the view. After updating the file (for example a new LaTeX run), the KDVI updates the file correctly but loses the position. Page number is OK, but the area in view is not any more the same. This is clearly a bug which is fairly inconvenient in real use. How to reproduce: 1) create a multipage document with 5 cm marginals at the top of the page and the bottom of the page, use small fonts (9pt) for the text. 2) view the document with KDVI 3) zoom the page in a way that BOTH the upper and the bottom marginal do not fit into the view and position the page in a way that the text area begins from the top of the view. 4a) rerun LaTeX on the file OR alternatively 4b) go to the next page by using PgDn 5) KDVI updates the file correctly, but loses the positioning of the view (the user has to move the view in the correct position by hand. This worked in correctly in the past) This bug a very annoying one and causes the use of KDVI to require much additional work. Expected behaviour is that the file is updated and the relative position of the view is kept the same (scrollbars do not move). When moving from page to page the expected behaviour is that the relative position of the next/previous page is kept the same (scrollbars do not move).
*** Bug 106888 has been marked as a duplicate of this bug. ***
If you use the continuous viewmode the relative position of the view is kept on reload.
SVN commit 427140 by whuss: Fix bug 107322 for single page mode. BUG:107322 M +1 -4 kmultipage.cpp --- trunk/KDE/kdegraphics/kviewshell/kmultipage.cpp #427139:427140 @@ -58,7 +58,7 @@ // Create ContentsList tableOfContents = new TableOfContents(sideBar); sideBar->addItem(tableOfContents, QIconSet(SmallIcon("contents")), i18n("Contents")); - + connect(tableOfContents, SIGNAL(gotoPage(const Anchor&)), this, SLOT(gotoPage(const Anchor&))); // Create MarkList @@ -516,9 +516,6 @@ ptr->setPageNumber(page); // Causes the zoomlevel to be updated if needed. emit viewModeChanged(); - // Make the widget &ptr visible in the scrollview. - scrollView()->moveViewportToWidget(ptr); - } else { // There are multiple widgets, then we are either in the // "Continuous" or in the "Continouous-Facing" view mode. In that
Sorry to be the one to open this, but this does not work even now - unfortunately. Some time ago I upgraded my system to another machine and a new version of SuSE Linux (now Novell). It seems that the problem still exists, at least it does not work as "Keep Position" works with xdvik (that is the right behavior). Please have a look at how that position works in xdvik. I would still prefer kdvi, it has so many other nice features. Unfortunately that one is too important for me... My current system is now: Please verify all fields and deselect any that are incorrect. 1 KDE Version 1.4 (KDE 3.5.1 Level "a" , SUSE 10.1) 1 Application DVI View Plugin 1 Operating System Linux (i686) release 2.6.16.21-0.25-default 1 Compiler Target: i586-suse-linux Application kdvi version 1.4. I'll prepare a proper file for you to test this... :-> Best regards, Jarmo Ahonen
I agree to Jarmo Ahonen's comments. In addition, I find it annoying that the viewport is lost every time the page is flipped. On most computer screens, a whole A4 page of 10pt text can hardly be read without scrolling. So every cm of white space on the display means lost resolution. With a "keep view" feature like in xdvi, it would be possible to set the viewport once to maximize the usable resolution, and then read through the document. This should be a small fix, but would be a huge usability improvement i my opinion. (also for kpdf etc..) Best regards, Nils Becker
kdvi is no longer maintained since KDE SC 4, and its functionality is replace by okular. If the issue in this report still exists in or apply to okular in KDE SC 4.10.5 or higher, please reassign the report to okular product or create a new report against okular.