4 ms·
I think the new behavior is great. First of all because it remembers both where I'm saving and where I've been exporting in my workflow, and second because fran
by jberryman 14y ago
I think the new behavior is great. First of all because it remembers both where I'm saving and where I've been exporting in my workflow, and second because frankly saving in GIMP's native format and creating a flat lossy JPEG that approximates the work you've been doing are really fucking different things, and I find it comforting that they choose to make that explicit. I can how if you open GIMP once a month to make a LOLCAT how this behavior could be annoying.
- Turing_Machine 14y agoWhat it should do is save the file in both XCF and the format the user actually wants. There could be a checkbox to turn off this behavior. That way it would satisfy both the elitists and the people who just want to do their jobs.
- cbhl 14y agoYou could submit a patch. :)
- sneak 14y agoYou could stop being an apologist. Neither will happen, though.
- Turing_Machine 14y agoI seriously doubt that they'd accept any patch that altered the One True Way that they've decided on.
- larrik 14y agoYeah, except that you can open a jpg, crop it, and then try to re-save it over itself, and then: Oh, no you can't. The work flow is really awkward then. You are exporting a jpg from a jpg? Oooookay....
- anoncow 14y agoSince you edited the jpeg, you might want to save the layer and other nfo in an xcf
- hellerbarde 14y agoYou can just select "Overwrite foobar.jpg" in the menu. You can even have a keyboard shortcut for it. That should solve all you guys' troubles :) cheers