From 4f0ccae3990bfe1c6ce268bfb3c22f7bfe9cfc0b Mon Sep 17 00:00:00 2001 From: Richard Kimberly Heck Date: Thu, 4 Oct 2018 20:37:03 -0400 Subject: [PATCH] Fix bug #9004. I'm not entirely happy with this way of doing it. It seems messy. But there is not another clear option right now. --- src/frontends/qt4/GuiView.cpp | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/frontends/qt4/GuiView.cpp b/src/frontends/qt4/GuiView.cpp index d1991aa08b..2fb58deb84 100644 --- a/src/frontends/qt4/GuiView.cpp +++ b/src/frontends/qt4/GuiView.cpp @@ -3709,15 +3709,21 @@ void GuiView::dispatchToBufferView(FuncRequest const & cmd, DispatchResult & dr) // Let the current BufferView dispatch its own actions. bv->dispatch(cmd, dr); - if (dr.dispatched()) + if (dr.dispatched()) { + if (cmd.action() == LFUN_REDO || cmd.action() == LFUN_UNDO) + updateDialog("document", ""); return; + } // Try with the document BufferView dispatch if any. BufferView * doc_bv = documentBufferView(); if (doc_bv && doc_bv != bv) { doc_bv->dispatch(cmd, dr); - if (dr.dispatched()) + if (dr.dispatched()) { + if (cmd.action() == LFUN_REDO || cmd.action() == LFUN_UNDO) + updateDialog("document", ""); return; + } } // Then let the current Cursor dispatch its own actions. -- 2.39.2