{"id":2083,"date":"2026-05-25T07:57:23","date_gmt":"2026-05-24T23:57:23","guid":{"rendered":"https:\/\/xlwings.net\/blog\/?p=2083"},"modified":"2026-03-28T06:16:45","modified_gmt":"2026-03-28T06:16:45","slug":"how-to-use-applicationdisplayexcel4menus-in-the-xlwings-api-way","status":"publish","type":"post","link":"https:\/\/xlwings.net\/blog\/how-to-use-applicationdisplayexcel4menus-in-the-xlwings-api-way\/","title":{"rendered":"How to use Application.DisplayExcel4Menus in the xlwings API way"},"content":{"rendered":"\n

The DisplayExcel4Menus<\/code> property of the Application<\/code> object in Excel’s object model is a legacy feature primarily retained for backward compatibility with older Excel 4.0 macro sheets (XLM). In modern Excel usage via xlwings, its practical application is very limited and specialized. This property controls whether the old Excel 4.0 menu bars are displayed in the application window alongside or instead of the standard command bars. In contemporary Excel versions, these classic menus are hidden by default, as the ribbon interface is the primary UI.<\/p>\n\n\n\n

Functionality:<\/strong>
The main function is to toggle the visibility of the Excel 4.0 menu bar. This can be useful in rare scenarios where you are maintaining or interacting with very old macro sheets that rely on those specific menu commands for execution or user interaction. For most modern automation and analysis tasks using xlwings, this property is not required.<\/p>\n\n\n\n

Syntax in xlwings:<\/strong>
In xlwings, you access this property through the app<\/code> object, which represents the Excel Application<\/code>. The property is a Boolean (bool<\/code>) value.<\/p>\n\n\n\n

# To get the current state\ncurrent_state = app.api.DisplayExcel4Menus\n\n# To set the state (True to display, False to hide)\napp.api.DisplayExcel4Menus = True<\/code><\/pre>\n\n\n\n
The property is a simple read\/write attribute. Setting it to True<\/code> makes the Excel 4.0 menus visible; setting it to False<\/code> hides them. Note that changes might only be fully apparent when working with an Excel 4.0 macro sheet (.xlm) as the active document.<\/p>\n\n\n\n
Code Examples:<\/strong>
Here are practical xlwings API examples demonstrating its use:<\/p>\n\n\n\n
    \n
  1. Checking the Current Status:<\/strong>
    This code checks if the legacy menus are currently displayed.<\/li>\n<\/ol>\n\n\n\n
    import xlwings as xw\napp = xw.apps.active # Get the active Excel application\nmenus_visible = app.api.DisplayExcel4Menus\nprint(f\"Excel 4.0 Menus Visible: {menus_visible}\")<\/code><\/pre>\n\n\n\n
      \n
    1. Toggling the Display:<\/strong>
      This script toggles the visibility state. It’s a good practice to restore the original state after your operation if you are temporarily changing it.<\/li>\n<\/ol>\n\n\n\n
      import xlwings as xw\napp = xw.apps.active\n\noriginal_state = app.api.DisplayExcel4Menus\nprint(f\"Original state: {original_state}\")\n\n# Toggle the state\napp.api.DisplayExcel4Menus = not original_state\nprint(\"Toggled display state.\")\n\n# ... Perform any tasks that require the menu state change ...\n\n# Restore the original state\napp.api.DisplayExcel4Menus = original_state\nprint(\"Original state restored.\")<\/code><\/pre>\n\n\n\n
        \n
      1. Ensuring Menus are Visible for a Legacy Macro:<\/strong>
        If you need to ensure the menus are visible before running an old command, you might use this pattern.<\/li>\n<\/ol>\n\n\n\n
        import xlwings as xw\napp = xw.apps.active\n\n# Force the menus to be displayed\napp.api.DisplayExcel4Menus = True\n\n# Assuming 'wb' is a workbook containing Excel 4.0 macros\n# wb.api.ExecuteExcel4Macro(\"SomeOldMacro()\") # Example of running an XLM macro\n\n# It is often advisable to hide them again afterwards to clean up the UI\n# app.api.DisplayExcel4Menus = False<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
        The `DisplayExcel4Menus` property of the `Application` object in Excel's object model is a legacy fe…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-2083","post","type-post","status-publish","format-standard","hentry","category-xlwings-api-reference"],"_links":{"self":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2083","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/comments?post=2083"}],"version-history":[{"count":2,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2083\/revisions"}],"predecessor-version":[{"id":3188,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2083\/revisions\/3188"}],"wp:attachment":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/media?parent=2083"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/categories?post=2083"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/tags?post=2083"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}