View Single Post
Old 04-01-2024, 10:10 PM   #6
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,736
Karma: 5446592
Join Date: Nov 2009
Device: many
It already exists via the new keyboard focus navigation:.

Code:
    // for keyboard focus navigation
    sm->registerAction(this, ui.actionFocusCodeView,    "MainWindow.FocusOnCodeView");
    sm->registerAction(this, ui.actionFocusBookBrowser, "MainWindow.FocusOnBookBrowser");
    sm->registerAction(this, ui.actionFocusPreview,     "MainWindow.FocusOnPreview");
    sm->registerAction(this, ui.actionFocusTOC,         "MainWindow.FocusOnTOC");
    sm->registerAction(this, ui.actionFocusClips,       "MainWindow.FocusOnClips");
Using the ui.actionFocus* will in fact make that DockWidget viewable (ie. open it) it you send focus to it. It works like that for all of the above, so no need to use or add shortcuts for the View menu that relates to these DockWidgets. That includes the ClipsWindow and the PreviewWindow.
KevinH is offline   Reply With Quote