Comment 12 for bug 1068529

Just an idea when thinking once more about the behaviour shown in test_altazi3.ssc:

The reason for the observed behaviour may be a parallel processing issue - if core.moveToAltAzi starts a separate thread for performing the movement, then a subsequent call to core.getViewAzimuthAngle would of course see the old position, since the motion is not yet complete. In this case, one might think about inserting a wait for completion of motion in the corresponding "get"-functions or declare this as responsibility of the script programmer (perhaps with a hint in the API description as suggested bove?!)...