PixInsight Forum (historical)
PixInsight => Bug Reports => Topic started by: Niall Saunders on 2009 April 05 11:46:44
-
Hi Guys,
I came across a problem the other day, when working with multiple workspaces (nine, to be precise).
I had a FITS image open in the ninth workspace, and wanted to double-check the FITS header for that image. However, every time I selected <FITS HEader> from the main <File> menu, nothing seemed to happen.
I gave up - I wasn't THAT concerned, and in fact attributed the 'error' to the fact that I had eight other Workspaces open, each of which had TWENTY-FOUR RGB images and one Greyscale image open. Basically, I was just amazed that PixInsight had not 'crashed' with the memory overload (4Gb RAM on Vista64, Core2Quad).
At some point, a few minutes later, I happened to select Wokspace 1 - and, lo and behold, there was the FITS Header window.
It was displaying the header for the image I had had open in Workspace 9 - just that it was being displayed in Workspace 1 instead.
Is this a bug?
Cheers,
-
Is this a bug?
Of course it is ;).
More scenarios:
- Run PixInsight, go to ws 3 and close. Open again, ws 3 is automatically selected. Open image, go to File > FITSHeader: it appears in ws 1. Go to ws 1 and close.
- Run PixInsight, ws 1 is selected. Go to ws 3, open image, go to File > FITSHeader: it appears in ws 1. Don't change ws and close.
- Run PixInsight, ws 3 is selected. Open image, go to Process > Image > FITSHeader, it appears in current ws. Close FITSHeader, move image to ws 2, go to ws 2, go to File > FITSHeader, it still appears in ws 3. Go to Process > Image > FITSHeader, it "moves" to current ws.
So it seems related to invoking the process from File instead of Process > Image. Let's see if the fix makes it into 1.5 ;).
-
Hi Niall and David,
I confirm that this bug has been fixed in version 1.5. Thank you for your reports.