You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having an ungodly amount of hotstrings. Without menu-hotstrings, that would be way too much.
I usually use them for annoying-to type words, or very specific things I don't have the energy to remember in detail (like the exact sequence (or just full name) of the C-Jun-amino-terminal kinase-interacting protein 1, about which I've had to write a 200-page report :P)
The syntax of the storage in file currently is *‖stoi..‖MCL‖En‖stoichiometric¦stoichiometry‖stoichiometry, or Options||Triggerstring||SendMethod||Status||Replacement(s).
I'd suggest, for Menu-hotstrings, to append a substring that's stored and updated on OnExit(): Options||Triggerstring||MCL/MSI||Status||Replacement(s)||Counter1/Counter2/Counter3/Counter4/Counter5/Counter6/Counter7
Then, when triggered, the menu is sorted according to previous usages. On selection, the respective timer is incremented, and the order is sorted again.
Without remembering too much on how/when the menu is created, it might be best to reorder after the insertion, so as to not induce perceivable lag between keypress and execution.
Thank you.
Sincerely,
~Gw
The text was updated successfully, but these errors were encountered:
I was thinking about it again. To me constant position of hotstring on menu list helps me to remember it. So I don’t see the advantage coming from this feature.
Hello,
I am having an ungodly amount of hotstrings. Without menu-hotstrings, that would be way too much.
I usually use them for annoying-to type words, or very specific things I don't have the energy to remember in detail (like the exact sequence (or just full name) of the
C-Jun-amino-terminal kinase-interacting protein 1
, about which I've had to write a 200-page report :P)The syntax of the storage in file currently is
*‖stoi..‖MCL‖En‖stoichiometric¦stoichiometry‖stoichiometry
, orOptions||Triggerstring||SendMethod||Status||Replacement(s)
.I'd suggest, for Menu-hotstrings, to append a substring that's stored and updated on
OnExit()
:Options||Triggerstring||MCL/MSI||Status||Replacement(s)||Counter1/Counter2/Counter3/Counter4/Counter5/Counter6/Counter7
Then, when triggered, the menu is sorted according to previous usages. On selection, the respective timer is incremented, and the order is sorted again.
Without remembering too much on how/when the menu is created, it might be best to reorder after the insertion, so as to not induce perceivable lag between keypress and execution.
Thank you.
Sincerely,
~Gw
The text was updated successfully, but these errors were encountered: