Mount horizon limits are enforced even when disabled
When moving the mount before capturing and the requested altitude is out of boundaries set in the Mount module, Capture displays a pop-up warning the end-user. However the pop-up appears even if the altitude limits are disabled.
if (minAlt != -1 && maxAlt != -1)
{
if (targetAlt < minAlt || targetAlt > maxAlt)
{
KSNotification::error(i18n("Requested altitude %1 is outside the specified altitude limit boundary (%2,%3).",
QString::number(targetAlt, 'g', 3), QString::number(minAlt, 'g', 3),
QString::number(maxAlt, 'g', 3)), i18n("Telescope Motion"));
return false;
}
}
Because it is possible to give a negative altitude in the Mount module limits, it is possible to change the altitude value to a lower value bypassing the pop-up, but there is a clash between the disable marker (-1) and the real altitude (-1 degree).
While working around this pop-up when using e.g. a flat box on a wall which happens to be slightly under the horizon is certainly possible knowing how the code behaves, a second pop-up appears later on preventing the slew procedure. This is another issue.