mir06
commented
9 years ago when the tracking status of the server is changed either by the manual control or by stellarium goto-command, the telescope-client has to show the new status in the gui. this has been done by calling GtkSwitch.set_active(boolean). But it seems that this routine emits the notify::activate signal. thus the onToggleTracking is called which itselfs toggles the tracking and switches of the tracking. I've changed the call to GtkSwitch.set_state(boolean) but this only sets the internal state of the switch and does not alter the gui. So more logic is needed to find out "who" changed the tracking status.
Hallo, den manuellen Druck am Taster wuerde ich loggen. Unter debug level findet sich folgenden Eintrag im log. DEBUG: 2015-03-06 18:27:34 stop tracking DEBUG: 2015-03-06 18:27:34 stop Azimuth motor DEBUG: 2015-03-06 18:27:34 BREAK -- Azimuth: actual_step/steps/direction: -12753 / 990 / 1 DEBUG: 2015-03-06 18:27:34 stop Altitude motor DEBUG: 2015-03-06 18:27:34 BREAK -- Altitude: actual_step/steps/direction: -99421 / 1872 / 0 DEBUG: 2015-03-06 18:27:34 INPUT -- Azimuth: actual_step/steps/direction: -12753 / 854 / 1 DEBUG: 2015-03-06 18:27:34 INPUT -- Altitude: actual_step/steps/direction: -99421 / 1735 / 0 DEBUG: 2015-03-06 18:27:34 stop Azimuth motor DEBUG: 2015-03-06 18:27:34 stop Altitude motor DEBUG: 2015-03-06 18:27:34 BREAK -- Altitude: actual_step/steps/direction: -99419 / 1735 / 0 DEBUG: 2015-03-06 18:27:34 BREAK -- Azimuth: actual_step/steps/direction: -12750 / 854 / 1 DEBUG: 2015-03-06 18:27:35 blink rate: 0.500000 DEBUG: 2015-03-06 18:27:37 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:39 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:41 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:43 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:45 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:47 blink rate: 2.000000 DEBUG: 2015-03-06 18:27:49 blink rate: 2.000000 Wieso endet das Tracking um 2015-03-06 18:27:35?
LG Stephan