https://issues.apache.org/ooo/show_bug.cgi?id=124525
--- Comment #8 from Andre <[email protected]> --- This bug is caused by the many ways of storing the current page and the many ways to notify changes of the current page. The slide sorter tries its best to keep track and coordinate these but, sometimes, fails to do so. In this special case the code to look at can be found in SlotManager::FuSupport() where the SID_UNDO and SID_REDO slots are processed. A SelectionObserver::Context is created before the actual undo or redo is executed that listens for newly inserted slides. If there are any then these slides are selected afterwards. The first of these, per standing rule of the slidesorter, becomes the new current page. In this case, however, there are no new slides. Therefore the SelectionObserver just deselects all pages when the Context is destroyed. The result is that the default slide (the first slide) is made the current slide. -- You are receiving this mail because: You are the assignee for the issue. You are watching all issue changes.
