Bug 184518 - View orientation changes during automatic reload
Summary: View orientation changes during automatic reload
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-16 15:10 UTC by Tristan Miller
Modified: 2011-06-26 06:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.7.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2009-02-16 15:10:29 UTC
Version:            (using KDE 4.2.0)
Installed from:    SuSE RPMs

Reproducibility: Usually

Steps to reproduce:

1. Compile the following LaTeX file to DVI or PDF with latex or pdflatex:

\documentclass{article}
\usepackage{lscape}
\begin{document}
foo
\begin{landscape}
bar
\end{landscape}
\end{document}

2. Open the output file in Okular.
3. Make sure Settings->Configure Okular->Reload document on file change is checked.
4. Scroll to the second page of the document.
5. View-Orientation->Rotate Right
4. Edit the lines "foo" and/or "bar" in the original file, save, and recompile.
5. Okular automatically reloads the file.

Observed behaviour:
6. Quite often (more than half the time), the view orientation in Okular changes back from landscape to portrait.

Expected behaviour:
6. Okular should not change the page orientation; it should have preserved the 90 degree rotation.
Comment 1 Christopher Reichert 2011-06-21 19:55:21 UTC
The problem here is that modifying the latex document and generating a new pdf often results in changing the criteria by which okular saves unique documents( mainly file size). This behavior probably only happens when the size of the file is changed due to your modifications.

You can check this in your local kde configuration directory.

I will talk with some of the other developers and see what can be done about this.
Comment 2 Christopher Reichert 2011-06-26 06:24:38 UTC
The fix has been applied to version 4.7.0