Currently the signal selection dialog and .json config files only work for builtin lcm types compiled with cpp macros, and not lcm messages discovered by the Python layer. Using the Python layer, it would be nice to allow exploration of LCM traffic via the user interface within signal-scope a la lcm-spy.
Currently the signal selection dialog and .json config files only work for builtin lcm types compiled with cpp macros, and not lcm messages discovered by the Python layer. Using the Python layer, it would be nice to allow exploration of LCM traffic via the user interface within signal-scope a la lcm-spy.