Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1 released
On 04/15/2011 08:17 PM, Michael Natterer wrote: ... Argh, it's 2.7.2 of course... ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On 2010-07-03 16:29, Jernej Simončič wrote: On Saturday, July 3, 2010, 22:01:50, photocomix wrote: snipsnip One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? Regards ... Alec ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Sunday, July 4, 2010, 11:27:35, Alec Burgess wrote: One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? The installer actually defaults to Program Files\GIMP 2, but you can change that if you choose Custom install. -- Jernej Simončič http://eternallybored.org/ Anything that begins well ends badly. Anything that begins badly ends worse. -- Universal Law ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On 2010-07-04 05:36, Jernej Simončič wrote: On Sunday, July 4, 2010, 11:27:35, Alec Burgess wrote: One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? The installer actually defaults to Program Files\GIMP 2, but you can change that if you choose Custom install. Sorry ... my bad ... on first install I missed the [Custom] button - I think because I was perplexed by the forced uninstall and clicked w/o thinking. After uninstall and reinstall everything is where I wanted it. Regards ... Alec ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Sorry ... my bad ... on first install I missed the [Custom] button - I think because I was perplexed by the forced uninstall and clicked w/o thinking. After uninstall and reinstall everything is where I wanted it. Regards ... Alec Maybe move the UNISTALL step after CUSTOM and add in CUSTOM a option to skip the Unistall will help a bit even if i would prefer see at the Unistall step a visible checkbox allowing to skip that PS soorry for the missed Re in the subject title...seems a little bug at gimpusers.com when using the forums...should be manually added as now -- photocomix (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 18:13:04, photocomix wrote: For not clear reasons the Windows installer of 2.7.1 force unistall of previous version of gimp That is correct. Apparently no way to skip unistall, or to cancell unistall/install process Apparently somebody is claiming things without even trying the installer. The point is i can't see any reason to force unistall, The point is that the new installer combines 32 and 64-bit GIMP in a common installer, and once it becomes stable, many people will be upgrading from 32-bit GIMP 2.6 - it would make no sense for these people to keep both GIMP 2.6 and 2.8 at the same time, so the new installer removes the old version first. Since this functionality needs to be tested before it's deployed in the stable installer, it's forced in the unstable one (the uninstall will be optional, but I haven't implemented that yet). -- Jernej Simončič http://eternallybored.org/ The more campaigning, the better. -- O'Brien's First Law of Politics ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 22:01:50, photocomix wrote: Sergey i tried the installer and i could not see how cancel or skip unistalling AT THE POINT OF UNISTALLING Judging from messages i see here Once the uninstaller is running, there's no way to cancel it - it wouldn't make any sense anyway, since some files are already deleted at that time, and there's no way to bring them back. This is why the installer displays a warning before it starts. However, since you are apparently the third person who ignored that dialog, I guess I'll have to bring the checkbox back. Sure? most (if not all) of third party plugin are not compiled for 64 bit but only for 32 so many may prefer run a 32 bit gimp even if a 64 bit version could be available By default, the 64-bit version installs everything needed to run 32-bit plug-ins as well (in fact, the 64-bit version always uses 32-bit TWAIN plug-in, since the 64-bit one doesn't work). BTW, please fix your e-mail program so that it doesn't strip Re: from subject. -- Jernej Simončič http://eternallybored.org/ Information which is true meets a great many different tests very well. -- Berkeley's Fourth Law ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Tor, and what solution can you advice? Now I can see two alternatives - to rename libraries and have UFRaw working, and do not rename libraries and do not use UFRaw. Tor Lillqvist wrote: after renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok Renaming DLLs is never a good idea. There might be a good reason why the name was changed - namely because the API and/or ABI has changed. --tml With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Tor, and what solution can you advice? File bugs with the respective maintainers to fix the problem? But yeah, that might take a while of course. So sure, if you know what you are doing, and you verify that it works, feel free to rename DLLs. But be aware then that telling about it might inspire random, more clueless, other people to repeat the trick without really knowing what they are doing. --tml ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
In the new release notes of http://www.gimp.org/release-notes/gimp-2.7.htmlthe keyboard shortcut for shrink wrap is still noted Ctrl+R, although it is now Ctrl+J. Same problem for Fit in Window. Incidentally, does this latter command appear in some menu? Same question for Alt+click in a layer thumbnail: what is the name of the command, and does it appear in some menu? Olivier Lecarme ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Hello Thank for the hard work. I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Von: Alexander Rabtchevich alexander.v.rabtchev...@iaph.bas-net.by I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). Can't reproduce. And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. Different version of the bz2 library, I guess. Regards, Michael -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Michael Schumacher wrote: Von: Alexander Rabtchevichalexander.v.rabtchev...@iaph.bas-net.by I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). Can't reproduce. Look at the navigation window. It is grey regardless GEGL preview is enabled or not. And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. Different version of the bz2 library, I guess. The above message is shown when gimp plugin is used. Entry point for the procedure g_assertion_message_expr is not found in the library lbglib-2.0-0.dll is shown when a standalone UFRaw version is launched - it uses its own bzip2.dll. Is there a way to overcome that? With respect, Alexander Rabtchevich attachment: window.jpg___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
The problem with UFRaw was caused by the deinstallation of 2.6 version made by 2.7.1. After renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok except bzip2 library - UFRawonly wants the old one. With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
after renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok Renaming DLLs is never a good idea. There might be a good reason why the name was changed - namely because the API and/or ABI has changed. --tml ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
