I know this issue has come up a number of times during the L6 lifecycle. And I'm sure you knew that negative comments on L7 wouldn't be long in coming. So my apologies, but...
I have a very fast machine - latest gen core i7, 32gb ram, Samsung 850 pro ssd. The right-click menu in this image took 5 seconds to populate.

Further, the 80-20 rule is completely backward. The stuff I use 80 percent of the time is inaccessible without scrolling (e.g. lexicons and dictionaries). And stuff that I use far less than 20 percent of the time is in the main place that my eyes are supposed to gravitate to. Most of the entries on the right below manuscript, lemma, and root I never use.
Here's another right-click menu which demonstrates another problem:

Note that entries on the right are not in the same order, and entries available in the first screen shot are not available in the second. This is understandable, to a point. But it demonstrates that the use of icons only to signify what an entry is supposed to represent are woefully inadequate. It's cute to make a text description available by hovering, but that means I either have to memorize the icons or that I have to keep hovering until I find what I want. The most-used workflows should require the least input on the part of the user. I acknowledge that I may be the anomaly.
I'll repeat suggestions that I have made previously:
- Allow the user to enable/disable and re-order sections of the right-click menu. The full right-click menu could always be available via something like shift-key + right-click.
- Allow the user to assign hot keys to either the function keys or, better, the alpha-numeric keys when the active panel isn't some kind of text entry field. I'd love to be able to put my mouse over a word and hit the 'B' key to bring up BDAG for that word.
- Allow the right-click menu to be resizable. Mine is a fixed ~600x500. If I could resize it, and Logos remembered that size, I could easily get everything to show up without scrolling. Further, there would be room to display the text descriptions of the entries on the right (manuscript, lemma, root, etc.).
Thanks for considering these suggestions. I love Logos, I live in it weekly for sermon preparation and study. I know that it's very exciting to add significant new features. But usability is a feature, too. And my core workflows for the tool are slower and less accessible than in the past because of the challenges that I've described.
Donnie