Comment 9 for bug 789691

Indeed, everything works fine if I stick to GMT. I had forgotten I had
changed that option.

With the patch, I now find no problem with the localtime option. The time
control works as expected now, no 100% CPU issues. I tried the patch on
both the 1.3 source and the svn head, and it worked fine with both. Thanks!

73

On , AA1VS <email address hidden> wrote:
> Glenn,

> Please find attached a patch for the time controller and the time engine

> that might help. It may require further testing and is preliminary.

> If you care for the bloody details, the Julian time functions use the

> calendar year and the gmtime functions use year-1900. This patch

> addresses that.

> Further comparisons between gpredict running in UTC mode and in localtime
> would be appreciated.

> ** Patch added: "UTC v local time patch for time controller"

> https://bugs.launchpad.net/ubuntu/+source/gpredict/+bug/789691/+attachment/2147262/+files/UTC_TIME_CONTROLLER.patch

> --

> You received this bug notification because you are a direct subscriber

> of the bug.

> https://bugs.launchpad.net/bugs/789691

> Title:

> problems with time control: wrong icon, 100% on manual time adjustment

> Status in “gpredict” package in Ubuntu:

> New

> Bug description:

> Binary package hint: gpredict

> If I try to change the day or slide the slider in the time control,
> gpredict stops responding and uses 100% of CPU.

> Also (and this may be unrelated?) the Time Controller dialog shows the
> wrong icon for the "Play Backwards" button.

> Ubuntu 11.04 (natty).

> Seen with both 1.1-7 nd 1.3 (Specifically, gpredict 1.1-7 from ubuntu.com
> natty/universe and also with gpredict 1.3-ppa4+natty from
> http://ppa.launchpad.net/gpredict-team/ppa/ubuntu/ natty/main.)

> To unsubscribe from this bug, go to:

> https://bugs.launchpad.net/ubuntu/+source/gpredict/+bug/789691/+subscribe