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
First of all: Thank you for the development of this add-on, although I have not yet used it (just installed), it is an awesome concept that will get anki closer to supermemo
Is your feature request related to a problem? Please describe.
Beacause the add-on uses alt+ numbers
I tried to use alt codes 24-27 to get ↑↓→←
And I the following message appears Please select an Incremental reading Deck
Describe the solution you'd like
Maybe find a way to set an optional toggle setting to
wait to see if you press other number pad besides 2
Alt + 2 wait 2 seconds (if nothing happens) → activate the equivalent action on add-on
Alt + 2 + 4 → get the arrow simbol ↑
Describe alternatives you've considered
I found a way around this by using unicode on AutoHotKey (which I already used for the alt code. Alt+Shift+Up would give me ↑)
Additional context
I was using Edit field during review when noticed this while reviewing
First of all: Thank you for the development of this add-on, although I have not yet used it (just installed), it is an awesome concept that will get anki closer to supermemo
Is your feature request related to a problem? Please describe.
Beacause the add-on uses alt+ numbers
I tried to use alt codes 24-27 to get ↑↓→←
And I the following message appears Please select an Incremental reading Deck
Describe the solution you'd like
Maybe find a way to set an optional toggle setting to
Describe alternatives you've considered
I found a way around this by using unicode on AutoHotKey (which I already used for the alt code.
Alt+Shift+Up
would give me↑
)Additional context
![image](https://user-images.githubusercontent.com/68022085/88678239-2466e500-d0e6-11ea-9aee-1b96a6948b87.png)
I was using Edit field during review when noticed this while reviewing
In some way, this feature is related to #51
The text was updated successfully, but these errors were encountered: