The worst thing in #Gimp is probably that annoying "Are you sure you don't want to save your work" after you saved it as TIFF/PNG/JPEG/Whatever, because for Gimp, the only valid save option is its own format that no one cares about. This is probably the first thing anyone asks me about when using Gimp: how can I disable this annoying dialog as I just *saved* my image with the export function.
The developers are against any option to help users, that is some serious anti-user behaviour. Sad 🙁
This entry was edited (1 month ago)
BohwaZ
in reply to BohwaZ • • •tisaac
in reply to BohwaZ • • •So, 99% does not need to use GIMP, isn't it ?
Why not using Pinta for instance ?
pinta-project.com/
Pinta: Painting Made Simple
PintaBohwaZ
in reply to tisaac • • •@tisaac It's not packaged by my distro, plus I have been using Gimp for the last 20+ years and I'm used to the keyboard shortcuts.
Also this is what is packaged in distros I install for people (Debian, Mint).
tTh
in reply to tisaac • • •@bohwaz
CmykStudent
in reply to BohwaZ • • •Hi! The problem is, before that was put in place, people were constantly reporting different issues, like "Why doesn't my image have transparency when I save it?" (because they saved as JPEG).
The current policy was put in place to try reducing data loss. We're happy to explore other options - we even have a dedicated UX repo to collect feedback, discuss design, and implement considered solutions: gitlab.gnome.org/Teams/GIMP/De…
Issues · Teams / GIMP / Design / GIMP UX · GitLab
GitLabjjjacq reshared this.
BohwaZ
in reply to CmykStudent • • •@CmykStudent I know, and it is a valid issue. I'm just asking to have an option in the preferences to go back to the previous behaviour. So that I, as a user, can have the choice and not have to actively fight the software I'm trying to use.
This was denied repeatedly on the issues I stumbled upon 🙁
🧊 freezr 🥶
in reply to BohwaZ • • •@BohwaZ @CmykStudent
It makes very sense, at the beginning looks akward, but eventually you realize that is better to separate the working files from the output files.
This also avoid unwanted file overwriting. This default is very sane.
BohwaZ
in reply to 🧊 freezr 🥶 • • •jjjacq
in reply to BohwaZ • •It's hardly a bother to just do the extra click, and at times it makes me pause and think do I want to save the xcf or let's flatten all the layers into one and just keep the jpeg. Sometimes saving the xcf will save a ton of work later.
Personally, I'm happy with Gimp as it is. I used to like the older version with all the windows floating around individually. The new version which is more like photoshop I guess, is slightly less convenient, but I'm getting used to it 😁
like this
tTh and CmykStudent like this.
tTh
in reply to jjjacq • • •@freezr @bohwaz @CmykStudent
jjjacq likes this.
jjjacq
in reply to tTh • •tTh
in reply to tTh • • •jjjacq likes this.
jjjacq
in reply to tTh • •tTh likes this.
BohwaZ
in reply to jjjacq • • •Yes it's a bother. I work on hundreds of files at a time.
@freezr @CmykStudent
🧊 freezr 🥶
in reply to BohwaZ • • •@BohwaZ @CmykStudent @jjjacq
Me too, but I recognize that changing habits can be frustrating; having an option to restore the legacy method might be worthy.
CmykStudent
in reply to BohwaZ • • •That's a fair point. I think there's a reluctance to re-add an option that historically caused problems, even if it would also solve other problems.
Ideally, we want to find a solution that takes care of both problems (faster saving while also reducing the chance of data loss). If someone proposed a good design for that, then we'd do our best to implement.
In the short term, you might try the Saver plug-in by @akkana which lets you bypass the split: github.com/akkana/gimp-plugins…
gimp-plugins/gimp3/saver.py at master · akkana/gimp-plugins
GitHubjjjacq likes this.
jjjacq
in reply to BohwaZ • •🤣