core.moveToAltAzi(90,XX) issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Stellarium |
Fix Released
|
Medium
|
gzotti |
Bug Description
I write here, because I did not receive any replies in the forum...
This is my problem (it affects all Windows versions of Stellarium, don't know on other platforms):
~~~~~~~~~~~
core.moveToAltA
~~~~~~~~~~~
If (X != 90 OR X != -90), the function works well and it considers the Azimuthal Y value. But this is not true if the Altitude value is set to 90 (or -90) degrees. In fact, if you call
core.moveToAltA
the moveToAltAzi moves ALWAYS the view with the "West" cardinal point at the bottom, never mind the Azimuthal value Y passed to the function moveToAltAzi().
The workaround could be putting a value for the Altitude next to 90.0 (i.e. 89.9): it works quite well, but not very well if the Azimuth value is 0 or 180 degrees.
Is this a behavior by design or is it a bug?
Thank you.
Related branches
Changed in stellarium: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: scripting |
Changed in stellarium: | |
importance: | Medium → Low |
importance: | Low → Medium |
Changed in stellarium: | |
assignee: | nobody → gzotti (georg-zotti) |
milestone: | none → 0.15.0 |
status: | Confirmed → In Progress |
Changed in stellarium: | |
status: | Fix Committed → Fix Released |
Changed in stellarium: | |
status: | Confirmed → In Progress |
Changed in stellarium: | |
status: | In Progress → Fix Released |
I can confirm this bug description - I did some extensive tests since I experienced unexpected behaviour when using core.moveToAltAzi in my own scripts in Stellarium 0.11.4, Windows 64-bit version. So I wrote some scripts just for testing purposes; the scripts and the corresponding logfiles are attached.
When testing, I found other kinds of unexpected behaviour. It seems to me that the functions core.getViewAlt itudeAngle and core.getViewAzi muthAngle when called after core.MoveToAltAzi return the altitude/azimuth values BEFORE the call of core.MoveToAltAzi call (cf. script test_altazi). Furthermore, core.MoveToAltAzi seems to have no effect if it is called in a loop as in the script test_altazi2.
I experienced more problems with core.MoveToAltAzi in my scripts (seemed to work correct sometimes, but sometimes produced erroneous results as wrong viewing directions even when called with altitude other than +/-90 degrees), but I cannot reproduce those effects by now.
Thank you!