You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is it, that on the Stellarium app for Windows, you can type in a date in and also go back to a BC date, but on the Stellarium Web you can't type in a date and have to keep your finger on the down arrow under the date to go back in time. Then when you approach the year zero and try to go to a BC date, it then goes to the date 1860 or something like that. It seems like an obvious oversight on the part of the developers. On the android app, you can type in a date and go back to a BC data no problem, but the only problem is, there are not the celestial objects I want to see as there are on the Stellarium Web. Can the Stellarium Web developers please fix this problem, so that I can type in a date and also go back to a BC date. Thanks James.
The text was updated successfully, but these errors were encountered:
Stellarium-web may just not be targeted at historical simulation but on a quick installation-free look what's up "now" or in the near future. The desktop version is. Those programs are independent pieces of software.
Why is it, that on the Stellarium app for Windows, you can type in a date in and also go back to a BC date, but on the Stellarium Web you can't type in a date and have to keep your finger on the down arrow under the date to go back in time. Then when you approach the year zero and try to go to a BC date, it then goes to the date 1860 or something like that. It seems like an obvious oversight on the part of the developers. On the android app, you can type in a date and go back to a BC data no problem, but the only problem is, there are not the celestial objects I want to see as there are on the Stellarium Web. Can the Stellarium Web developers please fix this problem, so that I can type in a date and also go back to a BC date. Thanks James.
The text was updated successfully, but these errors were encountered: