Open janagrc opened 4 years ago
Hello,
thanks for the report. This is very likely because currently in the web version setting manually a city in the location menu doesn't change the time zone, i.e. it still uses your local time zone (the one used by your computer). I agree we need a fix for this counter intuitive behavior.
Fabien
Ah, I see, thanks for letting me know. Are there any workarounds currently (other than resetting the local time on your machine to whatever the simulated locale is)?
For the moment, I'd say the best workaround would be to do the time conversion by yourself..
On Wed, Sep 2, 2020 at 11:57 PM Jana Grcevich notifications@github.com wrote:
Ah, I see, thanks for letting me know. Are there any workarounds currently (other than resetting the local time on your machine to whatever the simulated locale is)?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium-web-engine/issues/62#issuecomment-685993671, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4OQVCJOYFLM5P7ES7276DSD2WU3ANCNFSM4QJZZFMA .
I'm using Stellarium Web to determine the rise and set times of the Sun and other objects, but I noticed these are not correct for mid-Southern latitudes throughout the year. I compared Sydney and Durban through the year in both Stellarium Web and Stellarium OSX and the sunrise and sunset times are not in agreement. I thought at first Stellarium web may be using UTC instead of local, but that doesn't seem to be the case.
Thanks!