Some of them have left comments and precious feedback, so you’ve decided to work on it a bit more and incorporate their suggestions and ideas. If you have a backtrace for a crash or a warning, paste it here.Let’s say that this is, for example, an important essay that you’ve shared with many of your friends. Press Enter to save the file to the designated folder.Īctual result: Receive erroneous error message Additional information.Thank you and kudos to all the team!!!Īdd screenshot or other files if needed. It should be the other way around, right?īy the way, I love, love, love GIMP!!! It is truly great software, and especially for free. But it doesn't seem like I should have to reorganize my storage scheme to facilitate GIMP. I realize there is an simple workaround for this: just move my project folder to a different location. xcf file, it is trying to build the save path relative to the location of the file being edited and it doesn't "like" the fact that I'm saving it to a different parent folder?* Perhaps the issue is not with a simple path length but when GIMP goes to save the. But now, I am editing files located in a Dropbox folder (c:\users\username\dropbox\filelocationfolder). Now that I'm thinking about it, I never had an issue saving there under those circumstances. In those cases, though, I was editing a file located in the parent directory of the specified folder. It does seem strange since I have successfully saved to this folder using GIMP in the past. Additionally, if I shorten the path by saving to one of its parent folders along the path, it will save successfully. This is not, in fact, true since the folder does exist and I can save to it using other apps. *When saving project files to a project location, I continually get an error that GIMP is unable to create the file because the file or folder does not exist. xcf files to Windows locations that is shorter than the Windows limit Seems to be a limit on the path length for saving. Package: Installer from Description of the bug Note: bug reporters are expected to have verified the bug still existsĮither in the last stable version of GIMP or on updated development code
0 kommentar(er)
