| Summary: | Different setting of continuous view mode per windows does not work correctly | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Jonas Schürmann <me> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdedev, luigi.toscano, me |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=432441 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screencast: Okular continous view bug | ||
|
Description
Jonas Schürmann
2020-05-12 09:27:50 UTC
I just found out that this problem has been reported before and there was an attempt to fix this in bug 388952. I'm not sure if that changes made it already into Okular 1.10.0, but if these changes are in fact in Okular 1.10.0 the fix did not work. Bug 341318 is related to this, there saving continuous view for every document is described. One more comment, sorry for the incremental information: In bug 388952 it was claimed that these changes made it into 1.7.3 so it seems that the problem is not fixed yet. Others state that different settings for Continuous mode work in their Okular. How do the other view modes work for you (Single Page, Facing Pages, ...)?
> However if I turn on continuous view in one window, turn it off in a second
> window and come back to the first strange things happen. The view blocks
> completely until I toogle continous view 2 more times, the view is displayed
> continuously although the menu setting says otherwise, and so on.
This sounds more serious. I never noticed such behaviour. I had similar bugs while moving the Continuous option to the View Mode submenu, but I fixed them as far as I could test. Can you make a screencast, so the problem is clear?
Created attachment 129101 [details]
Screencast: Okular continous view bug
I created a screencast of the page lockup and attached it to this issue. Your screencast makes it clear, thanks. I would describe it as: When I toggle Continuous in another window, the PageView in the first window freezes. When I continue toggling in the other window, PageView eventually unfreezes. Did you observe other kinds of “The first window should act strange”? Right now I don’t have an idea what could cause this. There are more changes planned to scrolling, so I will not investigate yet. (Besides having little time.) Thank you for the bug report. Can we ask you to please check if this is still an issue with either Plasma 5.27 (the current LTS version) or Plasma 6.0.5 (the latest released version)? There have been improvements made between the time this bug report was updated and today. When I tried to reproduce this now, the behavior of Okular appears to have changed. 1. Open one document, turn on continuous view 2. Open a different document in a second window, turn off continuous mode in this window, switch to window1, scroll 3. Turn it back on in window2 (as shown in the screen recording), switch back to window 1, scroll I was able to successfully scroll in window1 after turning off continuous mode in window2, and also after turning it back on. (In reply to TraceyC from comment #7) > Thank you for the bug report. Can we ask you to please check if this is > still an issue with either Plasma 5.27 (the current LTS version) or Plasma > 6.0.5 (the latest released version)? There have been improvements made > between the time this bug report was updated and today. The work on triaging is great, but please remember that Okular is not related at all with Plasma. So the sentence above doesn't make any sense. My apologies for the confusion. The latest version of Okular is 24.02.2. Jonas, can you please re-test with the latest version of Okular available for your OS and let us know if you still see this bug? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |