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
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
I have a project that uses Ctrl+Enter for control. Tracking this in pure Elm requires keeping track of which keys are up or down à la ohanhi/keyboard-extra. But this method is error-prone as it runs into the problem described here in #1: if Ctrl is down, and the browser is not focused at the moment Ctrl goes up, the tracked state in Elm is still "down" (ohanhi/keyboard-extra only tracks ups and downs, not window blurs).
I guess giving access to modifier states isn't hard, but as suggested in the Readme I'll leave potential solutions out of the report :)
The text was updated successfully, but these errors were encountered:
Problem
I have a project that uses Ctrl+Enter for control. Tracking this in pure Elm requires keeping track of which keys are up or down à la ohanhi/keyboard-extra. But this method is error-prone as it runs into the problem described here in #1: if Ctrl is down, and the browser is not focused at the moment Ctrl goes up, the tracked state in Elm is still "down" (ohanhi/keyboard-extra only tracks ups and downs, not window blurs).
I guess giving access to modifier states isn't hard, but as suggested in the Readme I'll leave potential solutions out of the report :)
The text was updated successfully, but these errors were encountered: