(10-16-2024, 05:35 PM)flyAntiquarian Wrote:(10-16-2024, 08:42 AM)Ofnuts Wrote: An "undo group" has nothing to do with a "layer group". It is a functionality used in plugins that tells gimp that all the modifications done by the script should be lumped into a single undo, so you can undo the whole script action with a single Ctrl-Z instead of a using a Ctrl-Z for each change that the script has done (which in some scripts would take ages).
Starting/ending the undo groups is part of my boilerplate code so it is always part of the code and I have no version of the code without this.
If you can reproduce the problem on a small image please attach the XCF here and I'll check it out.
But IMHO this may be just the result of something else messing with Gimp's undo stack and O-B-P is just an innocent bystander. Does the problem show on a fresh image? Do you run other scripts?
Thanks for following up!
I attached an xcf that's just a blank white background, the text layer I used to generate the text path, the guide path, and the original and bent text path. I was able to get it to work once, but then it started throwing the error. If you want to try to recreate it on your system, just try to bend the text path and then undo it and try again. Usually it'll stop working after the first time. Occasionally it'll work twice. I've been using GIMP for over a decade and I've never seen this error message, but you're right it's probably something unique to my system since it seems to work fine for other folks.
I don't have a particularly customized install, so I completely wiped GIMP (including configuration and support files) from my system and reinstalled it. The issue persisted through that. After that I tried installing another of your scripts (text along path) and that seems to work fine. I also installed GMIC-qt, which also seems to work fine. Is there another one of your scripts that's more similar to bend-path I should try?
I'm on an Intel Mac btw if that matters. I don't have a Windows or Linux machine to test on but I should have some time to try it on a M2 mac later today.
Can't reproduce. Ran it 5-6 times in a row without problems. Even running with my debugging trace I can't see anything suspicious.