IRC Logs for #circuits Monday, 2016-07-11

*** Coldblackice has quit IRC09:29
*** Coldblackice has joined #circuits09:34
*** Coldblackice has quit IRC11:04
*** Coldblackice has joined #circuits11:10
*** Coldblackice has quit IRC11:45
*** Coldblackice has joined #circuits11:51
*** Coldblackice has quit IRC12:27
*** Coldblackice has joined #circuits12:55
*** Coldblackice has quit IRC13:15
*** qwebirc98828 has joined #circuits14:21
KathyHello, Just wondering what the best way is for a parent component to be notified when a child component has stopped?14:26
*** Coldblackice has joined #circuits14:42
*** Coldblackice has quit IRC14:52
*** Coldblackice has joined #circuits15:13
*** Coldblackice has quit IRC15:27
*** Coldblackice has joined #circuits15:48
*** Coldblackice has quit IRC15:57
*** Coldblackice has joined #circuits16:29
*** Coldblackice has quit IRC16:40
*** Danishman has joined #circuits16:50
*** Workster has quit IRC17:08
*** Coldblackice has joined #circuits17:34
*** Coldblackice has quit IRC17:47
*** Coldblackice has joined #circuits18:03
*** Coldblackice has quit IRC18:09
*** Coldblackice has joined #circuits18:52
*** Coldblackice has quit IRC18:59
*** Coldblackice has joined #circuits19:17
*** Coldblackice has quit IRC19:42
*** Coldblackice has joined #circuits19:50
KathyLet me ask another way.  I have a main app component with several components registered to it, some of them with nested components registered to them.  If the main app component tells a component registered to it to stop and unregister, what is the best way to know when that action has completed?20:53
KathySo I figured out that the issue is that some of the subcomponents have a default handler.  The main app component's "unregistered" handler is not being called for those components registered to it that have a default handler.  Is there a way to overcome this and have the "unregistered" handler always called?22:16
*** Danishman has quit IRC22:31

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!