Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: unlockAfter #3

Open
jinjor opened this issue Apr 5, 2017 · 1 comment
Open

Feature: unlockAfter #3

jinjor opened this issue Apr 5, 2017 · 1 comment

Comments

@jinjor
Copy link
Owner

jinjor commented Apr 5, 2017

I tried manual strategy but sometimes the frequency is too high.

With current API, we cannot chain Process.sleep and unlock command.
@vitiral
Copy link

vitiral commented Nov 13, 2017

I was looking for exactly this! I tried using elm-delay, but alas it takes a msg, not a Cmd msg.

For now I'm using it and creating a Unlock* msg, but my rendering pipe now has like 5 messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jinjor @vitiral