Draconian wrote:
I failed to mention the main reason I am staying with 2.6. There are many script writers out there that need to update their scripts to work in 2.8. Most recent example is the Voronoi plug-in I used in my Indicator light tutorial. 2.8 users cannot perform the tutorial without the resulting pattern being provided for them. I think Tile Shuffle is another one and I know there are numerous other scripts I can't think of right now. This pretty much hamstrings users like me who use these particular scripts quite often.
Is the construction of 2.8 such that it makes so many things obsolete? Is it a completely different engine? Was Gimp bought out by Chrysler or something? As a user, I find it extremely annoying that I have to fix, or compile, or wait for someone who knows how to create a version I can actually use like Lyle just had to do. The darn thing should work out of the box and I don't care to use the "throw-together" version. I'll wait until everything gets fixed, updated, compiled or whatever so it's useable for me. Like Erisian, I have a slow machine with only 3MB of RAM so with XP and my Win 7 32 bit laptop, I am limited as to what I can handle.
This is normally caused by changed Procedure Database Calls or the PDB.
The changes reflect in the scripts as depracated because a script may contain something like this
(gimp-layer-insert-new-layer layer)
<-- just an example
But the new PDB could be changed to something like this
(gimp-insert-layer layer)
<-- just an example
This will throw a error and sometimes it will stall the script.
You can see the new PDB calls via the Help>Procedure browser
Open that dialog and do a search for the line error.Old depracated calls are normally still contained within the dialog but will tell you to use another PDB call because that one is depracated.
The error dialog will usually give you the depracated call that caused the error.