The following bug and limitations are known. Please send new
bug reports, comments, suggestions to: saotng@head-cfa.harvard.edu:
There is no way to create an annulus region marker.
When the raw data is being transferred to SAOtng by the external
file access program, the GUI performance can slow down noticeably.
When a cursor shape is changed (e.g. from circle to rectangle) using
the (Button 3) marker menu inside the cursor, the button press actions inside
the cursor become confused. Only the right side of the inner area
responds to button presses.
SAOtng does not allow images loaded from IRAF to be re-scaled, as did
SAOimage.
Histogram equalization is slower than it was for SAOimage because it
performs the algorithm on the entire image rather than just a section.
Also, if the frame buffer is very large, the histeq algorithm can fail to
converge.
The external fitsextract program prints a warning when it detects
data overflow when summing extracted data; it should type cast up.
Loading regions whose positions are described in degrees can lead to
an inaccuracy of a fraction of a pixel.
Sending strings with unbalanced "{" or "}" to the SAOtng "message" xpa
has problems that we covered up by balancing the brackets at the end of
the string. Similar problems occur if a "\" is placed at the end of the
string.
When SAOtng is resized using the window manager, the color bar does
not resize. This causes problems with discrete colormaps.
The down arrow key of the panner occasionally gets "stuck" at zoom 4.
Sometimes a frame does not get deleted when the "Delete Frame" button is
pressed.
An "evaluation error" message sometimes is printed to SAOtng's stderr
when resizing the window.
If the BLANK keyword has a value of 0, SAOtng disables checking for
BLANK values for that image.
On Alphas, the error:
Error: Attempt to unmanage a child when parent is not Composite