A plugin panel takes the keyboard when it is on screen

What it is

A plugin's panel is not part of Omniscio's own screens. It is a separate, sealed page that Omniscio embeds, and a page like that only hears a keystroke while it is the one thing holding the keyboard. Before this change nothing ever handed the keyboard to it, so as soon as you clicked anything else — a sidebar row, a chat, the projects list — every key you pressed went to Omniscio, and the only way back into the plugin was to click inside its panel.

Where to find it

There is nothing to switch on. It is how every plugin's panel behaves once the plugin is installed and turned on: the panel you open from the plugin's sidebar row, and the same panel in its own window when you pop it out.

How it behaves

• Opening a plugin's panel gives it the keyboard, so the first key you press after opening it reaches the plugin.
• Switching to another plugin and then back hands the keyboard over again, so the panel you are looking at is always the one that hears you.
• A chat that opens over a plugin panel covers it; when that chat closes, the plugin takes the keyboard back.
• A text box elsewhere in Omniscio wins. If you are typing in a chat, a search field or an editor when a plugin panel comes to the front, you keep the keyboard and nothing you type is sent to the plugin.
• A plugin's panel shown as a small widget on a dashboard never takes the keyboard, and neither does the panel on a plugin's settings screen. Only a panel you opened as your main view takes it.
• On a phone or in the web version of Omniscio a plugin's panel is framed by the browser, and keyboard behaviour there is the browser's — this change is about the desktop app.

Related

The plugin marketplace page explains installing and turning plugins on, the plugin settings panel page covers a plugin's own settings screen, and the plugin widgets page covers the small dashboard panels a plugin can add.