GPredict should not stop tracking when another module is selected

[Aang23]

I was using GPredict to control my rotator, where I have several modules containing different categories of satellites I often track. FengYun-3B was set to be tracked in GPredict's rotator control window, opened from my "L-Band" module.

In the meantime, I was waiting for another satellite, FengYun-3E, to come around. So I checked in my "X-Band" module, realized I was a bit late and rushed outside, forgetting to switch back to the "L-Band" module.

When I came back, I realized GPredict's rotator control was frozen and did not track anything, I switched back to the other module and it carried along as it should.

Shouldn't the expected behavior be for GPredict to carry on tracking even when another module is selected if a rotator is being controlled?

[csete]

Hi @Aang23

Thanks for reporting this. I think this was an unintended side effect of trying to save CPU cycles when a module is hidden, which made sense 15 years ago but shouldn't be a problem today. I agree that tracking info for radios and rotators should be updated even when a module is not visible.