Currently it is the case that the plugin panels cannot be changed via userchrome.css. They don't "know" this file by default. But it should technically be possible to load the userchrome.css also into the plugin. I've already thought about this, but I'm not sure if it is currently supported by the plugin API.
Technical background:
It should be possible to add the stylesheet via joplin.views.panels.addScript('<PathToAppData>/userchrome.css'). However, I'm not sure if I can get the <PathToAppData> with the current plugin API or simply use a relative path like '../../userchrome.css'. I need to check that first.
I know zero about plugin development, but I have seen wordpress plugins that just have a textbox where you can put whatever css you want to be applied to the plugin aspect. Would that be an option? I realize it could be a nightmare. But maybe there is a way to filter the user input.
Honestly, I like the idea of having a central stylesheet where I can define the style of the App and all of its plugins. With this you also don't have to specify global styles (like font family) at multiple locations.
I guess I will add an option to "enable" the userchrome.css for the plugin. So users can still use the provided style options in the plugin settings.
Which version of Joplin are you using? The command ID is correct. Maybe the "q" must be specified in uppercase? Have you tried to set the shortcut directly in the shortcuts editor? Because this worked for me also with "ALT+Q".
I have checked whether or not it is possible to enable the userchrome.css for the plugin panel. Unfortunately it is not. It's a limitation of the plugin API. I will start another thread to discuss this. But I don't think that will be supported soon.
Yep, it's kind of weird that Electron makes a distinction between q and Q, because Shift is an accelerator, thus the letters could be case insensitive....
So, is this a history previous/next? I expected it to be a scroll left and right. Just curious.
Unrelated, I just noticed that when I hover over the tab bar and scroll the scroll wheel, the tabs actually move slightly up and down. Shift-scroll still moves left and right like before.
Any reason why you are directly changing the keymap.json file? Validation is quite strict on it because it's not meant to be user edited. Or was it not possible to do what you wanted using the app shortcut editor?
In my case there is no such entry in the shortcuts table for the command in question. This also happens in other cases. For instance I had to manually add "Toggle visibility" for the favorites plugin in keymap.json. Also, for some reason the changes made to this file were not persistent until I added the file to the profile directory.
Yes, that's because after installing the "Note Tabs" plugin, there was only one shortcut appearing in the editor. I think it was the "Pin Note" shortcut, all others were missing. After a bit of search I found that I could add the missing one after exporting the shortcuts, editing the file and then importing them.
Do you mean that you have disabled them in your own install, therefore you decided to add them into the plugin's interface?
I'd suggest that buttons to scroll the tab bar left and right might be more useful. Especially since new tabs don't auto focus yet (they can hide off to the right if too many tabs are open).
Better said I have hidden the editor toolbar via userchrome.css, because I don't need/use it. However, the navigation buttons, which I use quite often, also disappear. That's why I added them to the plugin.
I've already planned to fix the issue that new tabs might not be visible. I want the tab to always be visible when changing the selected note. So that possibly automatically scrolls to the right place. That's why I don't want to add extra buttons for it now.
Can you please share your solution? In other words, what did you put in keymap file or where I can dig out how exactly those commands look like? I'm interested in switch to next/previous tab mostly...
