sd/source/ui/sidebar/LayoutMenu.cxx |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 510f14518d90c0fbfb5c147132e3d7ac7850b4cb
Author:     Michael Weghorn <[email protected]>
AuthorDate: Wed Jan 21 12:33:38 2026 +0100
Commit:     Michael Weghorn <[email protected]>
CommitDate: Thu Jan 22 18:01:02 2026 +0100

    tdf#168281 sd: Don't set texts for slide layouts in icon view
    
    Don't set the layout names as strings to be displayed
    by the icon view.
    
    This aligns the vcl/SalInstanceIconView case with the
    gtk3 one where the texts are not displayed anyway, as well
    as with the behavior prior to
    
        commit cf523a77a76645f301aaa43b57b0c78c8c685561
        Date:   Thu Jun 12 22:28:06 2025 +0530
    
            tdf#166964 Switch to IconView in LayoutMenu for improved UI handling
    
    . It also fixes rendering issues and the problem of
    not enough space getting allocated to show all layouts at
    the same time for the vcl implementation, as described in
    tdf#168281.
    
    The layout names are still available via tooltips and
    as accessible names.
    
    Change-Id: Iaa0bd000344ef6d9a938f869dc22b1e50f96aa83
    Reviewed-on: https://gerrit.libreoffice.org/c/core/+/197738
    Reviewed-by: Michael Weghorn <[email protected]>
    Tested-by: Jenkins

diff --git a/sd/source/ui/sidebar/LayoutMenu.cxx 
b/sd/source/ui/sidebar/LayoutMenu.cxx
index 0a99ef3d0d35..47dd26289c97 100644
--- a/sd/source/ui/sidebar/LayoutMenu.cxx
+++ b/sd/source/ui/sidebar/LayoutMenu.cxx
@@ -489,7 +489,7 @@ void LayoutMenu::Fill()
                 else
                 {
                     Bitmap aPreviewBitmap = GetPreviewAsBitmap(aImg);
-                    mxLayoutIconView->insert(id, &sLayoutName, &sId, 
&aPreviewBitmap, nullptr);
+                    mxLayoutIconView->insert(id, nullptr, &sId, 
&aPreviewBitmap, nullptr);
                     mxLayoutIconView->set_item_accessible_name(id, 
sLayoutName);
                     mxLayoutIconView->set_item_tooltip_text(id, sLayoutName);
                 }

Reply via email to