Known SAOtng bugs and limitations

The following bug and limitations are known. Please send new bug reports, comments, suggestions to: saotng@head-cfa.harvard.edu:

There is no easy way to create an annulus-type 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.
If an incorrect filter specification is supplied to a QPOE file name (e.g "foo.qp[pha1-10]" instead of "foo.qp[pha=1-10]"), SAOtng will exit!
When an image is sent to SAOtng from IRAF's tv/display task, its coordinate system is flipped from what SAOtng expects. This causes SAOtng to track markers incorrectly.
SAOtng should allow images loaded from IRAF to be re-scaled, as SAOimage did.
Histogram equalization is slower than it was for SAOimage.
When a FITS image is displayed that contains non-trivial BSCALE and/or BZERO values, the scale display is wrong.
The external fitsextract program prints a warning when it detects data overflow when summing extracted data; it should type cast up.