Post by Big AlJust started happening recently. Before, the title would reflect the
name of the image.
Any ideas?
Just tested it with GIMP 2.10.30, the exported image still has the original name. Must be something else going on.
This reminds me of Mint's Text Editor (xed or gedit), which saves documents with no name as "unsaved document", which is really silly. It's untitled yes, but not "unsaved", it's sitting right there where I saved it. This is just stupid.
Hard to believe the maintainers of xed/gedit haven't noticed this yet. Or maybe they just don't care.
The saved/unsaved status is the * in front of the name, not the name.
I guess it would be more proper to use Document1/Image1 for a name rather than unsaved. I guess the programmers just sorta thought the user would name it as it is saved. A small flaw in logic, but it seems logical the user would name it on the way out.
For temp stuff, I'm constantly just saving it as Unsaved/Untitled.
There was a time, when a pane opened and you dumped text in it,
it was a "New Document", and if you did not like the name,
you would correct it during the Save() operation. It's a New Document,
because the pane started life in an undefined state, without an
existing file handle.
I'm seeing editors today that are stupid enough, to take the first
text you pasted and fill the file handle with that. Which is definitely
not what the user had in mind, and like all the other examples done
so far, indicates a lack of <cough> "perception".
feeling like a pig today.txt <=== um, not what I had in mind as a filename
I know working on text editors is considered boring for developers
and "beneath them", considering the sample code they had to write
to get their CS degree, but "work step by step and try harder".
Or an AI will get your job. AI's lack fit and finish.
The humans had better show the AI efforts up :-)
Paul