Focus on output log when starting

Anonymous avatarAnonymous created an issue

When I run Workbench from a shortcut (rather than inside a repository), it opens Repository Registry panel and focuses on it. In this case I can use the keyboard to select and explore one of the repositories in my list.

However, if in a previous session the Output Log was visibile, this panel will still be open next time I run the Workbench, and its current directory will be the current directory of the process that spawned it —on Windows I usually end up in %systemroot%\system32\. Moreover, the Log panel will hold focus, making it impossible to easily navigate the Registry.

The Output log should either be closed when no repository is selected, or at least the Registry should be focussed when Workbench is opened this way.

To reproduce:

  • open Workbench, make sure the Log is closed, close Workbench
  • re-open Workbench, verify that the Registry is focussed
  • open the Output Log, cloe Workbench again
  • re-open Workbench, the Log stole focus from the Registry

Keyboard-only workaround:

  • if the Output Log is visible, press Ctrl-L. The Log will close and focus will return to the Repository Registry

Comments (2)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.