sw/source/uibase/utlui/content.cxx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
New commits: commit 6c149bffd798d401db0945f6f3ee8ab777020298 Author: Jim Raykowski <rayk...@gmail.com> AuthorDate: Tue Aug 15 21:05:05 2023 -0800 Commit: Jim Raykowski <rayk...@gmail.com> CommitDate: Sun Aug 20 07:44:04 2023 +0200 SwNavigator: Save some cycles by using break instead of continue When a content change is detected the Display function will clear and recreate the content tree from the content type member arrays, therefore, when a content change is detected there is no need to continue the loop here to set tree entry user data, which may have been the reason for using continue. Change-Id: Id1bc6fe6dddac54aa7299d3921c9352dc2314f79 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155730 Tested-by: Jenkins Reviewed-by: Jim Raykowski <rayk...@gmail.com> diff --git a/sw/source/uibase/utlui/content.cxx b/sw/source/uibase/utlui/content.cxx index 5238dde260b6..bca6c625adc3 100644 --- a/sw/source/uibase/utlui/content.cxx +++ b/sw/source/uibase/utlui/content.cxx @@ -3055,7 +3055,7 @@ bool SwContentTree::HasContentChanged() { SAL_WARN("sw.ui", "unexpected missing entry"); bContentChanged = true; - continue; + break; } const SwContent* pCnt = pArrType->GetMember(j); @@ -3067,7 +3067,7 @@ bool SwContentTree::HasContentChanged() !(sEntryText == m_sSpace && pCnt->GetName().isEmpty())) { bContentChanged = true; - continue; + break; } } }