Thanks for a hint. Alas, this doesn't help it either. If I knew the reason for that error message, I might have been able to do something about it, or at least ask a more focused questions :-) Maybe, someone else could tip in?..
On Wed, Sep 16, 2015 at 8:39 AM, Sander Elias <[email protected]> wrote: > Easiest way to defer code to next cycle is using > `$timeout(codeIwantInNextCyle,0)` That is something that just is needed > sometimes. Usually when setting up stuff in 1 element, that you then need > in another element. This is indeed a code smell, and you should hand over > the data more explicit, so this crux isn't needed at all. But as I said, > sometimes you just have to wait a bit. > I don't have time to figure out what is the exact reason it needs to be > deferred in your use-case tough. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "AngularJS" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/angular/BqWfGESgSQI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
