I think the double-click / swipe examples are actually the things that need addressing. Throttling events from the DOM is a hard thing to do in TEA, is a very common requirement, and the transient state of the throttling operation (i.e setting/resetting timers) is not of interest to the model at the level that TEA operates. These things are plumbing.
On Friday, March 10, 2017 at 2:02:50 PM UTC, Martin Norbäck Olivers wrote: > > > > Like the double click or swipe example, but with a more complicated state. > The state for double click and swipe is pretty simple to model in Elm, it's > just a matter of saving the time of click and the number of clicks. > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
