Hello Larry
Sorry for being so slow in getting back to you.
If I've understood you, this is completely normal :-)
It is just a side-effect of PixInsight's object-oriented user interface. When you select an image (or a preview) on the Histograms window, its histogram functions are plotted on the bottom graph. This is what we call input histogram, that is, the histogram of the selected image in its current state.
When you move the sliders, or change any histogram parameter, the upper graph -the output histogram- shows you a prediction of what the histogram would look like after applying the transform.
Then, when you apply the histogram transform to the image, its histogram obviously changes, and these changes are immediately reflected on the Histograms window. So now you have the input histogram as was predicted, and the output histogram as it would be if you'd apply the same transform again.
This is a normal behavior, and there's nothing we can do to avoid it without violating the fundamental design rules behind our user interface's paradigm.
What happens is that the Histograms window remains active after applying the histogram transform, because it is independent on the target image, as are all processing windows in PixInsight. In other applications, the histogram window is a modal dialog that closes automatically when you apply it by hitting the Ok button.
The Histograms window in PixInsight is one of a few cases where the transformation being defined depends on the transformed image. Another example of this is the Resample window, where you are changing the dimensions of an image, and its new dimensions are also used to predict new dimensions... :lol:
In the new PixInsight Standard application, we are adopting some measures to minimize the effects of these "singularities" in our user interface. No system is perfect, and our object-oriented interface has so many advantages that a few singularities are of very minor importance, in our opinion. It's just a matter of getting accustomed to them.
Thank you
