https://bugs.kde.org/show_bug.cgi?id=419096
--- Comment #2 from David Hurka <david.hu...@mailbox.org> --- There are use cases, which are partially based on the lack of split view (Bug 169847) Imagine any long datasheet, where page 27 references some table cells on page 125. Or an instruction set summary, where branch conditions are explained on page 123 and the instruction of interest is on page 17562. You can’t scroll back and forth in such cases. Imagine that you review a slide show, which gives contrary information on slide 25 and slide 60, which is referenced at slide 81. So you need two instances to compare slide 25 and slide 60 side by side, and one instance to make annotations on slide 81. Imagine that you heavily annotate a document, and suddenly you want to see how it looked without the annotations. Imagine that you open a remote document, which is created on-the-fly, and changes with every reload. Even Kate, which was used as example for other applications switching instance instead of opening a document twice, can open the same document in multiple windows, although it has split view. BTW: The merge request for this is here: https://invent.kde.org/kde/okular/-/merge_requests/148 -- You are receiving this mail because: You are watching all bug changes.
