It would be much more useful for me if you could see the whole message On Monday, 19 December 2016 15:51:46 UTC+1, Wouter In t Velt wrote: > > Op maandag 19 december 2016 15:06:28 UTC+1 schreef Jeff Horemans: >> >> Can anyone give (concrete) examples wherein the debugger proved to be >> useful, even crucial, in resolving the problem or bug? >> > > The debugger for me is very useful to find out if Msg fired and in which > order. > When interacting with the DOM elements through custom event handlers (e.g. > on "dragleave"), I need to find out if the event fired at all, and in which > order. > > Especially when processing output from side effects (UI events in my > case), the debugger comes in handy. > Wish I could expand the message itself, but even in current version, > seeing which messages fired and in which order is useful. > > Going back through the messages that did fire, and then look up if my > model ended up correctly is quite useful. > (Way more friendly than Debug.log everything) >
-- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
