Date: prev next · Thread: first prev next last
July 2018 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=106374

--- Comment #10 from Mike Kaganski <mikekaganski@hotmail.com> ---
This one is easy to change, just

        case FN_UPDATE_CUR_TOX:
        {
            const SwTOXBase* pBase = m_pWrtShell->GetCurTOX();
            if(pBase)
            {
+                const bool bWasLocked = m_pWrtShell->IsViewLocked();
+                m_pWrtShell->LockView(true);
                m_pWrtShell->StartAction();
                if(TOX_INDEX == pBase->GetType())
                    m_pWrtShell->ApplyAutoMark();
                m_pWrtShell->UpdateTableOf( *pBase );
                m_pWrtShell->EndAction();
+                if (!bWasLocked)
+                    m_pWrtShell->LockView(false);
            }
        }
        break;

to void SwView::Execute(SfxRequest &rReq) in
C:\lo\core\sw\source\uibase\uiview\view2.cxx. Note though, that the update not
only jumps the view; it also moves the cursor position to the position just
before the index field (which is natural: the cursor is placed inside the
field, e.g. by right-clicking; the content of the field is regenerated - i.e.,
it is destroyed and recreated again; so the position is lost in the process;
and the content of the field might be very different after the update). So is
the change consistent from UX PoV?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.