Whenever I stop a PLC simulation in the python3-dev branch, I get the mentioned error and the simulator doesn't show stopped ...
Starting the Simulator seems good ...
I stop it and ...
The console shows this output ...
Latest build does not match with connected target.
PLC data transfered successfully.
PLCobject : No files to purge
PLCobject : NewPLC (6d9ba33efecd64ae4ff432f17c52ebc1)
(service.py:13335): Gtk-CRITICAL **: 08:45:27.790: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
PLC installed successfully.
PLCobject : PLC started
PLCobject : Python extensions started
(service.py:13335): Gtk-CRITICAL **: 08:45:27.793: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Starting PLC
PLCobject : PLC stopped
(service.py:13335): Gtk-CRITICAL **: 08:46:24.788: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
and started again ...
With console output ...
Successfully built.
PYRO connecting to URI : PYRO://localhost:61531
PLC did not provide identity and security infomation.
Latest build matches with connected target.
Latest build already matches current target. Transfering anyway...
PLC data transfered successfully.
PLCobject : NewPLC (6d9ba33efecd64ae4ff432f17c52ebc1)
(service.py:13335): Gtk-CRITICAL **: 08:50:37.938: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
PLC installed successfully.
PLCobject : PLC started
PLCobject : Python extensions started
(service.py:13335): Gtk-CRITICAL **: 08:50:37.942: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Starting PLC
I think it is actually working but the GTK tie in for the GUI is not quite right in this case. So this is not a critical bug IMHO.
Whenever I stop a PLC simulation in the python3-dev branch, I get the mentioned error and the simulator doesn't show stopped ... Starting the Simulator seems good ... I stop it and ... The console shows this output ...
and started again ... With console output ...
I think it is actually working but the GTK tie in for the GUI is not quite right in this case. So this is not a critical bug IMHO.