3 ms·
I totally see that it makes sense for some work flows, including the ones Gimp is probably most meant for. It was frustrating that for the people whose workflow
by imurray 10y ago
I totally see that it makes sense for some work flows, including the ones Gimp is probably most meant for. It was frustrating that for the people whose workflows were messed up, the developers were totally opposed to doing anything about it though. Kudos to the plugin author for rolling up her sleeves and providing a way out. Also kudos to the gimp developers for providing a plugin architecture that made such a customization an option.
- babuskov 10y agoIf they made Ctrl-E work when you load the file for the first time, none of this would be the problem.
- Jehan-Girin 10y agoI don't understand. Ctrl-e does work fine "when you load the file for the first time". Even to make extra sure (though I already was), I have tested it on a GIMP 2.8 and on GIMP master just now. That works.
- babuskov 10y agoHere, I recorded a video to show the problem: https://www.youtube.com/watch?v=SekYlC4ON_U https://www.youtube.com/watch?v=SekYlC4ON_U I tried with 2.8.14 and 2.8.18, both running on Mac OSX. As you can see the Command-E option only shows up after I do "Export as".
- schumaml 10y agoDid you try whether it works? If this was in your video, I didn't see it.
- babuskov 10y agoI tried, and even filed a bug report. It's "as designed": https://bugzilla.gnome.org/show_bug.cgi?id=769359 https://bugzilla.gnome.org/show_bug.cgi?id=769359 The whole idea around this and the way they decided it to work is a mess.