Option to pin the Navigation tab when it is docked as a document tab

0 vote

Published a day ago

Posted on behalf of: Dan
vo1

"I prefer using the Navigation panel as a tab in the main workspace instead of keeping it docked on the left side.

This allows me to maximize the available screen space for remote sessions. I also don't need the Dashboard, so ideally the Navigation tab should act as my main starting point.

The Navigation tab should remain the leftmost tab, with new sessions opening to its right.
Ideally, there should be an option to pin the Navigation tab in a fixed position.

Desired Workflow
My preferred layout is:
- Navigation displayed as a tab in the main workspace.
- Navigation remains the leftmost tab.
- New sessions open to the right of the Navigation tab.
- Editing entries does not change the currently active tab.
- No Dashboard required.

This layout provides significantly more usable screen space while still allowing quick access to the Navigation tree.

Request: Please consider allowing the Navigation tab to remain fixed in position and retain focus after editing entries."

Eduard Sepulveda Lopez

All Comments (2)

Michael Beaudin

Published 17 hours ago

Hello,

There is currently a bug with the "Pin tab" feature in the right click menu of any tab, but it technically already exists. Once it is fixed, the navigation pane should be pinnable which should achieve the desired result.

Best Regards,

Michaël Beaudin

Danvo1

Published 7 hours ago

Hi Michaël,

Thanks for the clarification! Good to know that the "Pin tab" feature already exists and just needs a fix.

One additional question: Are you also aware of the focus issues when Navigation is docked as a tab?
Specifically, after saving an entry or the application settings, RDM automatically switches to another tab instead of keeping the previously active tab in focus. Ideally, RDM should always return to the tab that was active before opening the dialog, whether that's Navigation or any other tab.

These issues have already been reproduced and forwarded to the developers in the original bug report. I just wanted to make sure they're also being addressed.

Thanks again for your help!