Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Sven Neumann s...@gimp.org writes: On Fri, 2009-01-09 at 08:14 +0700, Charles wrote: The FileOpen plugin can be found here http://asso.lsf.05.free.fr/telechargement/image/gimp/?M=A Great, thanks a lot! I tried it with GIMP 2.6.4, it worked but we need to create a new image first before the menu become active, otherwise the menu is disabled. Also the file open dialog appeared behind the image window. I tried it with GIMP 2.4.5: Here, the dialog opens nicely in front of the image window, and the WinOpen menu option is available if an image is open OR gimp has just been started (i.e. it's only disabled if an image has been opened and closed). So, it works perfecly fine for me. :-) At least the first issue can easily be addressed. The plug-in should use the empty string as image-type parameter in the procedure registration. It probably uses * which means activate this plug-in if there's an image, no matter what image type. Thanks. The source code is not included in the above download link, but there's a text file containing the author's contact info, so if anyone is interested in taking over maintainance of that plug-in, it shouldn't be difficult to get the source (might be easier than starting from scratch). Greetings, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi, On Fri, 2009-01-09 at 08:14 +0700, Charles wrote: The FileOpen plugin can be found here http://asso.lsf.05.free.fr/telechargement/image/gimp/?M=A I tried it with GIMP 2.6.4, it worked but we need to create a new image first before the menu become active, otherwise the menu is disabled. Also the file open dialog appeared behind the image window. At least the first issue can easily be addressed. The plug-in should use the empty string as image-type parameter in the procedure registration. It probably uses * which means activate this plug-in if there's an image, no matter what image type. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
2009/1/8 Elwin Estle chrysalis_reb...@yahoo.com: I eject mine every time. Gimp is the only program that has this problem. I use Inkscape with it and it works fine. The problem is not that any particular user (you) does not eject disks properly. The problem is that the OS is designed to have disks ejected improperly. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Dotan Cohen dotanco...@gmail.com writes: 2009/1/7 Jernej Simončič jernej.listso...@ena.si: On Wed, 07 Jan 2009 22:19:03 +0100, Sven Neumann wrote: No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. It does this with removable drives because users rarely bother to eject (unmount) them before unplugging them. You can enable caching (which greatly improves performance), but then you have to remember to eject the device before disconnecting it, or you risk filesystem corruption. No, users rarely bother to eject (unmount) them before unplugging them because the OS works like this. If the OS said bad boy! and lost data _once_ then the users would stop. IIRC, that's exactly how it was in Windows 2000. Caching was enabled by default, and you got a bad boy! error message when removing the device. And yes, it was possible to lose data that way. This is a case of the OS fostering bad habits by treating the users as idiots who are unable to learn something so simple as pressing an eject button before physically removing hardware. Well, apparently most of the users *were* idiots unable to learn ..., because they had to change that behaviour in Windows XP. Greetings, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
On Thu, 8 Jan 2009 13:15:47 +0100, Jernej Simončič wrote: On Thu, 8 Jan 2009 01:11:48 +0200, Dotan Cohen wrote: No, users rarely bother to eject (unmount) them before unplugging them because the OS works like this. If the OS said bad boy! and lost data _once_ then the users would stop. Windows 2000 did that. Users were not happy. Also, why should the user have to dismount the volume at all? Why would he need to care about such things? -- Jernej Simončič http://deepthought.ena.si/ Contact address: jernej simoncic at isg si ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
On Sat, Jan 3, 2009 at 11:35 PM, Heinrich Moser use...@heinzi.at wrote: Hi! Short question: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? I remember that there was a plug-in for this a long time ago (which added Windows Open and Windows Save As menu options) but I cannot find that anymore. The FileOpen plugin can be found here http://asso.lsf.05.free.fr/telechargement/image/gimp/?M=A I tried it with GIMP 2.6.4, it worked but we need to create a new image first before the menu become active, otherwise the menu is disabled. Also the file open dialog appeared behind the image window. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi, On Sun, 2009-01-04 at 01:24 +0100, Heinrich Moser wrote: I don't think I will further investigate this, since I don't see much point in this, to be honest. Yes, we could find out what's taking GIMP's file open dialog so long and make it be as fast as other GTK applications. But I really think the time is better spent solving the problem permanently (like implementing the above mentioned plug-in) rather than fine-tuning something that can never be as fast as the native OS implementation. The above mentioned plug-in will always only be a kludge as it can't provide all the features that an internal file dialog offers. So the focus should be on fixing the GtkFileChooser. There is absolutely no reason why it can't be as fast as the native OS implementation. After all it is using native OS-specific code. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi, On Sat, 2009-01-03 at 18:16 -0800, Elwin Estle wrote: I wonder if a problem I have had with saving files from Gimp in Windows is somehow related. If I save direct to the local hard drive, there isn't much of a problem. But if I try to save to say, a flash drive plugged into the same computer running Gimp, or to a network drive, then file save times get really long. Yes, you expect those two situations to take a bit longer, but not that long. I can save an .xcf file to the local drive and then transfer it to a flash drive or a network drive and it is loads faster than trying to save directly from Gimp. (which is what I typically do, save first to the local hard drive, then transfer the file to the drive I actually want to store the file on.) No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. So an application writing a file with lots of file I/O calls will get miserable performance for slow drives. Copying the complete file to that drive will transfer the data in much larger blocks and thus yield reasonable performance. This is not the case on Linux for example. There the operating system will take care of combining many small file I/O operations into large buffer accesses. We might be able to work around this limitation by porting the XCF load and save routines and all file plug-ins to GIO, the VFS API that was recently added to GLib. Then we could use a GBufferedOutputStream which would do the buffering at the application level. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Sven Neumann s...@gimp.org writes: On Sun, 2009-01-04 at 01:24 +0100, Heinrich Moser wrote: I don't think I will further investigate this, since I don't see much point in this, to be honest. Yes, we could find out what's taking GIMP's file open dialog so long and make it be as fast as other GTK applications. But I really think the time is better spent solving the problem permanently (like implementing the above mentioned plug-in) rather than fine-tuning something that can never be as fast as the native OS implementation. The above mentioned plug-in will always only be a kludge as it can't provide all the features that an internal file dialog offers. So the focus should be on fixing the GtkFileChooser. There is absolutely no reason why it can't be as fast as the native OS implementation. After all it is using native OS-specific code. Well, that's how it should be in operating systems. To be honest, I don't think this is the case with Windows. Microsoft is well known for using undocumented OS features to make their applications more performant than their competitor's, so I guess they'd do that even more in something they consider part of the OS (rather than an application or a library), such as the file chooser. Nevertheless, as a user of GTK-based products, I really appreciate your effort on motivating people to improve GTK. And I don't want to leave this discussion without giving a big THANKS to all gimp developers for making such a great product! Please consider my request for a Windows file open/save dialog as an improvement suggestion (or as a plug-in suggestion, in case any motivated C developers read this) and not as criticism of your work or of your design decisions. Best greetings from snowy Austria, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
On Wed, 07 Jan 2009 22:11:37 +0100, Sven Neumann wrote: The above mentioned plug-in will always only be a kludge as it can't provide all the features that an internal file dialog offers. So the focus should be on fixing the GtkFileChooser. There is absolutely no reason why it can't be as fast as the native OS implementation. After all it is using native OS-specific code. I personally find the GTK+ widget so bad compared to the native Windows one that I usually resort to dragging images from Explorer when I want them opened in GIMP (and I don't use Explorer for file management, but my usual file manager works in console and thus doesn't support drag and drop). -- Jernej Simončič http://deepthought.ena.si/ Contact address: jernej simoncic at isg si ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
On Wed, 07 Jan 2009 22:19:03 +0100, Sven Neumann wrote: No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. It does this with removable drives because users rarely bother to eject (unmount) them before unplugging them. You can enable caching (which greatly improves performance), but then you have to remember to eject the device before disconnecting it, or you risk filesystem corruption. -- Jernej Simončič http://deepthought.ena.si/ Contact address: jernej simoncic at isg si ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
2009/1/7 Jernej Simončič jernej.listso...@ena.si: On Wed, 07 Jan 2009 22:19:03 +0100, Sven Neumann wrote: No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. It does this with removable drives because users rarely bother to eject (unmount) them before unplugging them. You can enable caching (which greatly improves performance), but then you have to remember to eject the device before disconnecting it, or you risk filesystem corruption. No, users rarely bother to eject (unmount) them before unplugging them because the OS works like this. If the OS said bad boy! and lost data _once_ then the users would stop. This is a case of the OS fostering bad habits by treating the users as idiots who are unable to learn something so simple as pressing an eject button before physically removing hardware. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Thanks for the information...BTW, Windoze isn't my OS of choice. I sometimes use Gimp at work, where we are pretty much stuck with Windows (Unless I want to go to the trouble of booting a Linux live CD). At home I have Linux and Mac OSX (Gimp runs kinda funky on OSX...but since I have Linux, I don't worry about it too much.) --- On Wed, 1/7/09, Sven Neumann s...@gimp.org wrote: From: Sven Neumann s...@gimp.org Subject: Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog To: chrysalis_reb...@yahoo.com Cc: gimp-user@lists.xcf.berkeley.edu Date: Wednesday, January 7, 2009, 4:19 PM Hi, On Sat, 2009-01-03 at 18:16 -0800, Elwin Estle wrote: I wonder if a problem I have had with saving files from Gimp in Windows is somehow related. If I save direct to the local hard drive, there isn't much of a problem. But if I try to save to say, a flash drive plugged into the same computer running Gimp, or to a network drive, then file save times get really long. Yes, you expect those two situations to take a bit longer, but not that long. I can save an .xcf file to the local drive and then transfer it to a flash drive or a network drive and it is loads faster than trying to save directly from Gimp. (which is what I typically do, save first to the local hard drive, then transfer the file to the drive I actually want to store the file on.) No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. So an application writing a file with lots of file I/O calls will get miserable performance for slow drives. Copying the complete file to that drive will transfer the data in much larger blocks and thus yield reasonable performance. This is not the case on Linux for example. There the operating system will take care of combining many small file I/O operations into large buffer accesses. We might be able to work around this limitation by porting the XCF load and save routines and all file plug-ins to GIO, the VFS API that was recently added to GLib. Then we could use a GBufferedOutputStream which would do the buffering at the application level. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
I eject mine every time. Gimp is the only program that has this problem. I use Inkscape with it and it works fine. --- On Wed, 1/7/09, Dotan Cohen dotanco...@gmail.com wrote: From: Dotan Cohen dotanco...@gmail.com Subject: Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog To: Jernej Simončič jernej.listso...@ena.si Cc: gimp-user@lists.xcf.berkeley.edu Date: Wednesday, January 7, 2009, 6:11 PM 2009/1/7 Jernej Simončič jernej.listso...@ena.si: On Wed, 07 Jan 2009 22:19:03 +0100, Sven Neumann wrote: No, that is because your operating system of choice sucks at file I/O. Windows does not buffer access to flash and network drives. It does this with removable drives because users rarely bother to eject (unmount) them before unplugging them. You can enable caching (which greatly improves performance), but then you have to remember to eject the device before disconnecting it, or you risk filesystem corruption. No, users rarely bother to eject (unmount) them before unplugging them because the OS works like this. If the OS said bad boy! and lost data _once_ then the users would stop. This is a case of the OS fostering bad habits by treating the users as idiots who are unable to learn something so simple as pressing an eject button before physically removing hardware. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Short question: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? I remember that there was a plug-in for this a long time ago (which added Windows Open and Windows Save As menu options) but I cannot find that anymore. Long explanation (i.e. why would I want this): The reason that I want this is because the GIMP dialogs are terribly slow when accessing a slow (e.g. VPN) UNC network path (= \\IP-Address\Share\directory\...). For comparison: After choosing a directory, GIMP takes ~20-40 seconds before showing the contents (the dialog being unresponsive during that time). On the other hand, Thunderbird (to use another multi-platform open-source product for comparison) pops up the default Vista file save dialog, which shows the directory contents almost instantly. I'm not sure if this is a GIMP bug or not; it's quite possible that Microsoft is doing some behind-the-scenes magic here (caching, undocumented functions, whatever) that causes it to be a whole lot faster than any other custom-made file chooser implementation. I'm using a workaround currently (putting the network directory in offline mode before using GIMP, which causes the UNC share to be redirected to a local cache directory; and synchronizing afterwards), but I really wish I wouldn't have to. Greetings, TIA, Heinzi * e.g. by using the GetOpenFileName/GetSaveFileName API functions ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
2009/1/3 Heinrich Moser use...@heinzi.at: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? I remember that there was a plug-in for this a long time ago (which added Windows Open and Windows Save As menu options) but I cannot find that anymore. There seems to be a NIH syndrome in many programs, Gimp included, where the devs feel (possibly rightly in many cases) that they must reimplement core OS functionality. File Chooser dialogs are among the most visible (and annoying) of these cases. Although you use Windows, here is my Kubuntu bug about the situation: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/281834 -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Sven Neumann s...@gimp.org writes: On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? No. And we are certainly not willing to add such an option. OK, thanks for the information. In that case, I can just hope that such a plug-in turns up again somewhere. The reason that I want this is because the GIMP dialogs are terribly slow when accessing a slow (e.g. VPN) UNC network path (= \\IP-Address\Share\directory\...). You should report this as a bug against GTK+ then and perhaps you will also want to help the GTK+ developers to isolate and fix the cause for this. Thanks for the pointer into the direction of GTK. To verify this, I've just downloaded gedit. It seems to use the same file open dialog library (except for the preview), but, surprisingly, it is indeed faster than GIMP (~10 seconds to show the directory contents, as compared to ~30 with GIMP). Greetings, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Win32: Use standard Windows File Open/Save dialog
I understand why it is the way it is, which is why I mention that it is sometimes the 'right' decision. However, end users don't like it, no matter what the technical merits may be. Also, each application obviously has it's own special needs, and the OS default File Chooser cannot satisfy them all. Maybe the GTK library (GtkFileChooser, to be specific) could show the native Windows dialog, if available? One standardised file chooser can't satify all needs, but a solution is that there are hooks and other mechanisms that allow applications to extend the file chooser. However this should be discussed in a GTK forum/mailing list. -- Richard H. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi, On Sun, 2009-01-04 at 00:17 +0100, Heinrich Moser wrote: Sven Neumann s...@gimp.org writes: On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? No. And we are certainly not willing to add such an option. OK, thanks for the information. In that case, I can just hope that such a plug-in turns up again somewhere. You can easily write such a plug-in yourself, in case there's really no way to locate the old one. It should be a trivial plug-in to write for someone who knows the Windows file-chooser API. You should report this as a bug against GTK+ then and perhaps you will also want to help the GTK+ developers to isolate and fix the cause for this. Thanks for the pointer into the direction of GTK. To verify this, I've just downloaded gedit. It seems to use the same file open dialog library (except for the preview), but, surprisingly, it is indeed faster than GIMP (~10 seconds to show the directory contents, as compared to ~30 with GIMP). You should investigate this then. It seems rather unlikely that GIMP is doing something with the file-chooser that could be responsible for this. What GTK+ version are you using with GIMP and which with gedit? Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
I wonder if a problem I have had with saving files from Gimp in Windows is somehow related. If I save direct to the local hard drive, there isn't much of a problem. But if I try to save to say, a flash drive plugged into the same computer running Gimp, or to a network drive, then file save times get really long. Yes, you expect those two situations to take a bit longer, but not that long. I can save an .xcf file to the local drive and then transfer it to a flash drive or a network drive and it is loads faster than trying to save directly from Gimp. (which is what I typically do, save first to the local hard drive, then transfer the file to the drive I actually want to store the file on.) --- On Sat, 1/3/09, Sven Neumann s...@gimp.org wrote: From: Sven Neumann s...@gimp.org Subject: Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog To: Heinrich Moser use...@heinzi.at Cc: gimp-user@lists.xcf.berkeley.edu Date: Saturday, January 3, 2009, 6:44 PM Hi, On Sun, 2009-01-04 at 00:17 +0100, Heinrich Moser wrote: Sven Neumann s...@gimp.org writes: On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: Is it possible to make GIMP use the default Windows File Open/Save dialog*, for example, by setting some secret configuration option? No. And we are certainly not willing to add such an option. OK, thanks for the information. In that case, I can just hope that such a plug-in turns up again somewhere. You can easily write such a plug-in yourself, in case there's really no way to locate the old one. It should be a trivial plug-in to write for someone who knows the Windows file-chooser API. You should report this as a bug against GTK+ then and perhaps you will also want to help the GTK+ developers to isolate and fix the cause for this. Thanks for the pointer into the direction of GTK. To verify this, I've just downloaded gedit. It seems to use the same file open dialog library (except for the preview), but, surprisingly, it is indeed faster than GIMP (~10 seconds to show the directory contents, as compared to ~30 with GIMP). You should investigate this then. It seems rather unlikely that GIMP is doing something with the file-chooser that could be responsible for this. What GTK+ version are you using with GIMP and which with gedit? Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
