(tool-preset-path-writable "/home/YOUR_USERNAME/.gimp-2.8/tool-presets") (tool-preset-path "/home/YOUR_USERNAME/.gimp-2.8/tool-presets:/opt/gimp/usr/share/gimp/2.0/tool-presets") (gradient-path-writable "/home/YOUR_USERNAME/.gimp-2.8/gradients") (gradient-path "/home/YOUR_USERNAME/.gimp-2.8/gradients:/opt/gimp/usr/share/gimp/2.0/gradients") (palette-path-writable "/home/YOUR_USERNAME/.gimp-2.8/palettes") (palette-path "/home/YOUR_USERNAME/.gimp-2.8/palettes:/opt/gimp/usr/share/gimp/2.0/palettes")
(pattern-path-writable "/home/YOUR_USERNAME/.gimp-2.8/patterns") (pattern-path "/home/YOUR_USERNAME/.gimp-2.8/patterns:/opt/gimp/usr/share/gimp/2.0/patterns") (dynamics-path-writable "/home/YOUR_USERNAME/.gimp-2.8/dynamics") (dynamics-path "/home/YOUR_USERNAME/.gimp-2.8/dynamics:/opt/gimp/usr/share/gimp/2.0/dynamics") (brush-path-writable "/home/YOUR_USERNAME/.gimp-2.8/brushes") (brush-path "/opt/gimp/usr/share/gimp/2.0/brushes:/home/YOUR_USERNAME/.gimp-2.8/brushes") (environ-path "/home/YOUR_USERNAME/.gimp-2.8/environ:/opt/gimp/usr/lib/gimp/2.0/environ") (interpreter-path "/home/YOUR_USERNAME/.gimp-2.8/interpreters:/opt/gimp/usr/lib/gimp/2.0/interpreters") (module-path "/home/YOUR_USERNAME/.gimp-2.8/modules:/opt/gimp/usr/lib/gimp/2.0/modules")
Gimp 2.8.22 whats new windows#
2.8 is actually pretty good, if you count thousands of hours of use in Linux and Windows without crashes or any major frustrations (I can't actually recall any frustrations I had with 2.8 at the moment.).
Gimp 2.8.22 whats new plus#
So very much of that sort of thing, plus new bugs, and some pretty wicked awful performance degradation. Anyway, that's "broke as fuck", as the kids would say. This is particularly important when you're using layer-level effects that don't show when the layer visibility is off. In 2.8, you can simply click the layer you want to work in, square select where you know the object is, float the selection, and click it to drag it even though it's completely hidden by upper layers. This the big one that makes 2.10 "unusable" for me, because I rely on that feature of GIMP a bajillion times a day. So.Įven fundamental stuff, like moving a floated selection that is in a layer "behind" another is impossible, if you can't "click through" the upper layer onto a visible portion of your floated selection.
Gimp 2.8.22 whats new how to#
I basically would have to learn how to use GIMP all over again.
In trying the later versions of GIMP, I found that some of the options that I used were no longer there, or some of the options that I used were completely changed. Thank you for your time and consideration!
Given how version 2.10.x of GIMP is in many ways a different program than the one that came before it, I am hoping that version 2.8.18 can remain in the Devuan repo for future releases. Indeed, Devuan ASCII comes with 2.8.18, so it's not a problem here yet, but I see that version 2.10.x will be included in the next Devuan release and that may well be a problem for folks like me. (I could go into the specifics if need be).įor now it's easy enough to simply uninstall 2.10.x and continue using 2.8.x. Even the performance and stability is utter garbage in both Linux (Mint 19) and Windows (10), in general, but especially when compared to 2.8.x in the exact same environment/hardware. Sadly GIMP 2.10.x is definitely a case where newer does not translate into better.Īnyway, in my experience the 2.10.x versions have broken the work flow and functionality of much what I actually use in GIMP to create graphics ( for example, GIMP source files are linked from there) to the point where the program is no longer usable. I would imagine that there isn't a large volume of GIMP users, so it's probably very easy for their development team to do whatever they like, despite bug reports and user feedback.
0 kommentar(er)
