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.getViewAltitudeAngle and core.getViewAzimuthAngle 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.
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!