don't always set tooltip.keyBindingCommand#308
don't always set tooltip.keyBindingCommand#308aminya wants to merge 1 commit intoatom-community:masterfrom
tooltip.keyBindingCommand#308Conversation
We can certainly make a PR to Atom, and see why this key-binding adding takes time. I uploaded the branch that I ported the Atom's tooltip function: We can also add the key-binding to the actual text instead of going through Atom's code. tooltip.title = tooltip.title + this.options.callback |
I prefer that 100% over just removing this feature from the tool-bar. But it's probably because it needs to find the keybind value in a rather large set of callback possibilities, though that doesn't mean it cannot be optimized.
That won't work. The callback value, in the case if-branch you removed is entered, is not the keybind string itself, it is the command name. |
I see. Thanks for the clarification. We can look into the actual function. The performance is not that bad though, but we may able to boost it a bit. |
That means we can close this PR, right? Again, though, I'm not against adding an option that disables this feature 😉 |
|
Let's keep it open for the future reference. If I close it, it might get lost 😄 |


Button creation time:
After:

Before:

This is not shown in the loading time of
tool-barsince other packages add buttons using the service, but instead, it can be easily measured usingwindow.performance.now()