[Feature Request]: Add setting to toggle/show Screenshot & Video functions inside the Menubar dropdown menu

[dennyschroeder]

Hi @richiemcilroy,

To keep the native Menubar dropdown menu highly customizable and clean for different workflows, it would be amazing to have a toggle option in the settings to show or hide the Screenshot/Video functions within the menu.

Current Behavior:
The dropdown list contains all screenshot actions by default, which might clutter the interface for users who solely use Cap for video recording or prefer to access screenshots exclusively via global hotkeys.

Proposed Solution:
Add a simple switch/toggle inside the "Shortcuts" or "Screenshots" settings panel (e.g., labeled "Show in menu" / "Im Menü anzeigen") right next to the hotkey configurations.

• If enabled, the corresponding screenshot action remains visible in the Menubar dropdown.
• If disabled, the action is hidden from the dropdown menu, allowing for a completely minimalist, maybe video-focused menu layout while still keeping the global shortcut active.

GR, Denny

[linear]

CAP-717

[tembo]

Some context that might help with implementation:

The tray menu is built in apps/desktop/src-tauri/src/tray.rs, specifically the build_tray_menu() function starting around line 381. The menu items for recording/screenshot modes are added in a section around lines 420-470 where items like TrayItem::RecordDisplay, TrayItem::RecordWindow, TrayItem::RecordArea, and TrayItem::TakeScreenshot are conditionally constructed based on the current RecordingMode.

There's already a pattern for dynamically hiding/showing menu content: the should_use_minimal_onboarding_tray_menu() function (line 333) conditionally renders a minimal menu during onboarding. A similar approach could be used here - read visibility settings from the settings store and conditionally skip adding certain menu items.

For settings storage, the existing GeneralSettingsStore in apps/desktop/src/utils/general-settings.ts already has toggle patterns for things like hideDockIcon and enableNotifications. New boolean fields like showScreenshotActionsInMenu or showVideoActionsInMenu would fit naturally there.

The toggle UI could go in the hotkeys settings page (apps/desktop/src/routes/(window-chrome)/settings/hotkeys.tsx) since it already displays the screenshot/video hotkey configurations - adding a "Show in menu" toggle next to each would follow the pattern suggested in the issue. The ToggleSettingItem component from Setting.tsx provides the existing toggle UI pattern.

Note that the refresh_tray_menu() function already exists for updating the menu dynamically, so when a visibility setting changes, calling that function would update the menu without requiring an app restart.

This pairs nicely with #1854 (showing keyboard shortcuts in the menu) - both could be tackled together since they involve the same tray menu construction code.