To be clear, Geany does not know anything about the existence of any plugin or the contents of any tabs it adds to Geany notebooks, even plugins included in the Geany project itself. Therefore plugins are entirely responsible for the behaviour of their UI. Plugins should connect to the relevant signal eg "switch-page" or "focus-tab" or "clicked" on the tab or whatever and then implement the behaviour they require.
Remember I said elsewhere the tab and the contents are different things, and in standard GTK the tab can be focussed instead of the content by clicking it when the page is current. That is the standard behaviour of GTK Notebook, and is how the Documents and Symbols tabs behave. Geany modifies it for the editor notebook to move the focus by intercepting the signals and returning focus to the content (the editor widget) as well as other actions the click might invoke, and the plugin can do so for its tabs if it wishes.
Geany provides a plugin API and that is all the interaction it has with plugins, it has no knowledge of what a plugin might do or what its UI is. A plugin can add pages to the sidebar notebook using standard GTK calls and techniques without any interaction with Geany as the notebook widget is exposed in the API.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.