IRC Logs for #circuits Tuesday, 2020-01-07

*** Oxygene has joined #circuits06:12
*** Oxygene has quit IRC06:34
*** ke4roh has joined #circuits12:40
*** robert_ has quit IRC15:09
*** Coldberg has joined #circuits15:24
*** C-Man has quit IRC15:26
*** C-Man has joined #circuits15:34
*** Coldberg has quit IRC15:35
*** kdb_ has joined #circuits16:15
*** kdb_ has quit IRC16:28
*** kdb_ has joined #circuits16:28
*** Oxygene has joined #circuits17:38
*** ke4roh_ has joined #circuits17:47
*** ke4roh has quit IRC17:50
*** ke4roh__ has joined #circuits18:48
*** ke4roh_ has quit IRC18:51
*** ke4roh__ has quit IRC21:15
*** riot has joined #circuits21:15
riotohai :)21:15
*** Oxygene has quit IRC21:21
rioti have a component that creates instances of, is there a way to make the component aware that an exception happened during e.g. port opening, without listening for exception events? i.e. is classic try:/except: possible somehow? I'd like to handle the problem where i possibly created it21:24
riot(among other reasons: to see which line of code exactly caused it. I have many components spawning and opening serial ports in the project :)21:25
*** robert_ has joined #circuits21:33
*** robert_ has quit IRC21:33
*** robert_ has joined #circuits21:33
riotif that isn't possible, can i somehow find out (e.g. in an exception event handler) that my component triggered it?21:50
*** kdb_ has quit IRC22:00

Generated by 2.14.0 by Marius Gedminas - find it at!