Hi Juan, thanks for you prompt answer.
I guess the confusion is because Vista here is not set to display the file extension, and probably does not display them in the file save box. This is combined in a maybe not totally expected behavior of the save function.
In vista 32 bits I can reproduce it as follow:
- Open A Copy of a file wihch exists only with a single extension, say tiff (testnew.tiif)
- Save As: the name is displayed without the extension on my system
type a new name without an extension (say blabla)
select the type jpeg
type record
You see the jpeg dialog and the file is saved normally.
Type save as again, you are prompt with the dialog with the original file name and original type (tiif in my case) and not the one of latest saveas, which in itself is a little bit trange but ok. The file name shows without extension on my system.
At that point if I first select the file type (FITS) then type the file new file name (blabla), I got the problem. But not if I do the operation in the other order.
The reasons seems to be that when I type the new file name, of which there is juste one (the jpeg one), windows does some autocompletion or something, see that there is a file name blabla.jpeg, and decide to change the type directly based on the extension. This is not visible by the extension name is hidden, and because we type OK to complete the name entry, so event if the type is updated, we close the dialog before we can see the type change. Fortunately because it is jpeg it prompts witha dialog and I see that it is not the expected type.
I love completion mode but not auto-completion...
Maybe making extension visible will lower the risque of confusion? Maybe not changing the file type when the user explicitely set the type (but rather changing the extension ? May be an alert if the user request type does not match the extension type ? It seems a log of work to do for a function which should not pring any surprise.
Thanks and have a good day, I'll go back to processing the images.
bitil
