[Rock-dev] Vizkit.control destroys configurations

[Alexander Duda]

You should always call Vizkit.control log at the very end just before 
Vizkit.exec because it does a lot of things preparing the replay. None 
the less it should not mess up the current path. Can you write an issue 
on github?

Some examples how to use it can be found here:
http://rock-robotics.org/stable/documentation/graphical_user_interface/300_displaying_logfiles.html

Best
Alex



Am 23.02.2016 um 14:59 schrieb Martin Günther:
> Dear list,
>
> I've just spent 2 hours debugging a stupid problem, and I thought I'd
> share it with the list, so it can either be fixed or documented.
>
> In my ruby scripts, I had this (shortened):
>
>      Bundles.initialize
>      Bundles.run 'laserscanner_tracking_filter_kalman' do
>          ...
>          Vizkit.control log
>          ...
>          filter = Orocos::TaskContext.get "laserscanner_tracking_filter_kalman"
>          Orocos.conf.apply(filter, ["default", "laserscanner_tracking"], true)
>          ...
>          Vizkit.exec
>      end
>
> That gave me the following error:
>
>      orocos.rb[WARN]:   /home/martin/rock/tools/orocos.rb/lib/orocos/configurations.rb:726:in `resolve_requested_configuration_names': no configuration available for multisensor_tracking::KalmanFilterLinearTask
>
> ... which sent me looking in all the wrong places. In the end,
> it turned out that moving "Vizkit.control log" after the
> "Orocos.conf.apply" line fixed the problem. So something inside
> Vizkit destroyed the available configurations.
>
> Is this a bug? If it's a feature, it should be documented somewhere...
>
> Cheers,
> Martin
>