Re: [Gimp-user] A Sad case of regression.
On 06/14/2013 02:34 PM, Steve Kinney wrote: Every time people insist on cluttering the list up with weeping and wailing and gnashing of teeth over Save vs. Export, it is... +1 -- KevinO ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression.
Repeat after me : Alt-F A, ctrl-s, ctrl-s (repeat as needed), shift-ctrl-e, close. Hardly rocket science and needs about 15 minutes for mucles memory to cut in. Jusy my 2d worth, F xx --- Apologies for brevity, top posting and poor citation.This email was sent from a mobile device. --- ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
No less than six digests were waiting to be read this morning, almost entirely cluttered with this nonsense. How much do I pay for the Gimp? Nothing. Am I delighted with it? Yes! Does it require any effort to get used to using ctrlE and ctrlS ? No - a child would make less fuss than some of the posters to this group. Thousands of us owe a debt of gratitude to all the developers. To the whingers - you are boring, get a life. Dave Russell London ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
From: Helen etter...@gmail.com snip I work with agents for my art galleries. One of my agents wants everything sent as jpeg so I send her what she wants. One wants .tif so I send her what she wants. Juried exhibits ask for jpeg (I don't know why but this change adds hours to a job that should take me half an hour. I fail to understand why using ctrlshiftE rather than ctrlshiftS adds any time at all to your work. What's happening in those extra hours? Dave Russell London ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, 15 Jun 2013 11:32:45 +0100 . traml...@gmail.com wrote: How much do I pay for the Gimp? Nothing. Am I delighted with it? Yes! Glad to hear you are. Does it require any effort to get used to using ctrlE and ctrlS ? No - a child would make less fuss than some of the posters to this group. You are missing the point here, that now if a user opens and modifies a .jpeg picture, Save does not replace the original with the modified picture, but creates a modified picture in a different format, which is contrary to all software practice, except in some cases (like Audacity) where Save explicitely saves a Project and not the original file. (Note to self: suggest to Tsar Alexander he modifies menu entry from Save to Save Project) And GIMP recognizes the difference, since it then complains that the picture has not been saved if you Export (to the original formai) then attempt to close the program. Thousands of us owe a debt of gratitude to all the developers. Yes we do, but we also owe it to them to give some feedback on how we feel about the changes they make in the app. To the whingers - you are boring, get a life. This is a bit rich, coming from the country where we hear they are still whingeing about Decimalization and Metrication ;-3) Cheers, Ron. -- Any man who hates dogs and babies can't be all bad. -- Leo Rosten, on W.C. Fields -- http://www.olgiati-in-paraguay.org -- ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
Hi all I not often write here, but I'm a regular user of gimp. But I slowly get upset by some mails here On Sat, Jun 15, 2013 at 11:32:45AM +0100, . wrote: No less than six digests were waiting to be read this morning, almost entirely cluttered with this nonsense. How much do I pay for the Gimp? Nothing. Am I delighted with it? Yes! Does it require any effort to get used to using ctrlE and ctrlS ? No - a child would make less fuss than some of the posters to this group. Thousands of us owe a debt of gratitude to all the developers. To the whingers - you are boring, get a life. Dave Russell London ---end quoted text--- +100 First: I am myself developer of open source projects as well as Debian developer, so not some casual user. These bullying emails are just plain rubbish. Software should be written with the users in mind. And - opening a jpg file - editing - saving should result in a saved version of yhe original file, because that is what practically all programs are doing, and what the user expectation, and natural behaviour is. Of course a program does not need to follow the guide lines, but then there should be a clear indication that it is doing something else than the standard/default/expected behaviour. It could all be easily avoided if there were two entries save as gimp doc and save as original and a config setting for the default shortcut binding. I don't mind gimp devs pushing for xcf format, what I dislike is breaking of expected behaviour and, like above emails, ignorance of the problem. Norbert ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 06/15/2013 01:36 PM, Renaud (Ron) OLGIATI wrote: This is a bit rich, coming from the country where we hear they are still whingeing about Decimalization and Metrication ;-3) Well, at least went metric, they didn't remain overly attached to their old warty version of a measurement system :) ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, 15 Jun 2013 12:29:37 +0100 . traml...@gmail.com wrote: I fail to understand why using ctrlshiftE rather than ctrlshiftS adds any time at all to your work. Not the time, but the annoyance at the stupidity of being told my file has not been saved, when I have just saved it back to its original format through Export. Cheers, Ron. -- Nothing is always absolutely so. -- Theodore Sturgeon -- http://www.olgiati-in-paraguay.org -- ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, 15 Jun 2013 08:18:37 -0500 Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote: Well, at least went metric, they didn't remain overly attached to their old warty version of a measurement system :) Actually they still use imperial measurements as well. The conversion over to metric wasn't 100% successful from what I hear. They still use Miles on roads, and Pints in pubs... Cheers, Ron. -- Nothing is always absolutely so. -- Theodore Sturgeon -- http://www.olgiati-in-paraguay.org -- ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 06/15/2013 02:28 PM, Norbert Preining wrote: Hi all I not often write here, but I'm a regular user of gimp. But I slowly get upset by some mails here First: I am myself developer of open source projects as well as Debian developer, so not some casual user. These bullying emails are just plain rubbish. Software should be written with the users in mind. And - opening a jpg file - editing - saving should result in a saved version of yhe original file, because that is what practically all programs are doing, and what the user expectation, and natural behaviour is. Of course a program does not need to follow the guide lines, but then there should be a clear indication that it is doing something else than the standard/default/expected behaviour. It could all be easily avoided if there were two entries save as gimp doc and save as original and a config setting for the default shortcut binding. I don't mind gimp devs pushing for xcf format, what I dislike is breaking of expected behaviour and, like above emails, ignorance of the problem. Norbert +10 Hi This strange save, save as behaviour could not exist in a professional environment. A professional (and many amateurs) user know he has to save his work. I think Gimp-2.8 tries to do instead of the user that it should do himself. It looks like an other OS (not GNU/LINUX) philosophy : anticipate the desire of the user. -- Maderios ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, 15 Jun 2013 15:57:57 +0200 maderios mader...@gmail.com wrote: This strange save, save as behaviour could not exist in a professional environment. A professional (and many amateurs) user know he has to save his work. I think Gimp-2.8 tries to do instead of the user that it should do himself. It looks like an other OS (not GNU/LINUX) philosophy : anticipate the desire of the user. And, worse, Tsar Alexander refuse to allow users to choose how they work. But thanks to Akkana, resistance is not futile... Cheers, Ron. -- Il faut se garder de donner un nom aux choses: Tant qu'elles n'en ont pas, elles n'existent pas, ou elles existent à peine. -- Jean Dutourd -- http://www.olgiati-in-paraguay.org -- ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ?
Date: Sat, 15 Jun 2013 11:30:43 +0200 From: schum...@gmx.de To: gimp-user-list@gnome.org Subject: Re: [Gimp-user] A sad case of regression ? . . . That's not perfect yet - for example, you lose the undo history . . . How often is Undo history ACTUALLY needed by the user, beyond fixing a ten-seconds-ago mistake? I can't personally name a single application that stores undo history with the document's workfile; but if you can, let me know. -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression.
Date: Sat, 15 Jun 2013 02:02:58 +0400 From: alexandre.prokoud...@gmail.com To: gimp-user-list@gnome.org Subject: Re: [Gimp-user] A Sad case of regression. On Sat, Jun 15, 2013 at 1:55 AM, Psiweapon wrote: Excuse me, Alexandre, but you're being DISMISSIVE AS HELL here. Yes, I am. AND being perfectly civil at the same time. :) As for the rest . . . well, I can sympathize that the if you don't like it, don't use it line is an almost Godwin-class argument. (There, I said it.) -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 06/15/2013 04:38 PM, Renaud (Ron) OLGIATI wrote: On Sat, 15 Jun 2013 15:57:57 +0200 maderios mader...@gmail.com wrote: This strange save, save as behaviour could not exist in a professional environment. A professional (and many amateurs) user know he has to save his work. I think Gimp-2.8 tries to do instead of the user that it should do himself. It looks like an other OS (not GNU/LINUX) philosophy : anticipate the desire of the user. And, worse, Tsar Alexander refuse to allow users to choose how they work. But thanks to Akkana, resistance is not futile... In developers world, women are rare. Some links concerning Linux geekette Akkana Peck http://www.shallowsky.com/software/ http://lanyrd.com/profile/akkakk/ http://lanyrd.com/2012/pycon/spckd/#link-hcgh http://geekfeminism.wikia.com/wiki/Akkana_Peck http://gimpbook.com/ https://plus.google.com/112662956693744460184/posts -- Maderios ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
well, i gotta say, that were i ever to actually use the gimp in any heavy capacity, or a company i worked at would, these saving lists would be required reading due to the variety of formats/procedures detailed. thanks, i guess. :) dan On Sat, Jun 15, 2013 at 1:18 PM, Chris Mohler cr33...@gmail.com wrote: On Sat, Jun 15, 2013 at 8:33 AM, Renaud OLGIATI ren...@olgiati-in-paraguay.org wrote: I fail to understand why using ctrlshiftE rather than ctrlshiftS adds any time at all to your work. Not the time, but the annoyance at the stupidity of being told my file has not been saved, when I have just saved it back to its original format through Export. See, now this I don't get. Instead of the dialog in 2.6 that was You can't include layers, paths, etc. in JPEG, flatten image?, now there's a dialog that's Hey you might have exported but you didn't save your layers, paths, etc, save them? - and somehow this is so vastly different? I was against the current behavior at the beginning, but my GIMP work falls into one of two cases and it works out this way: 1.) Without a net - destructive editing - I need to edit something like a 1-bit TIFF or a greyscale PNG. - The file is already the result of export from a complex vector file. - And all I really need to do is make some bits black, or some bits white. - Most of the time, I don't use layers or masks - if it's getting too complex I need to go back to the vector source and correct there, then do another export. - So, I open, edit, export, close the file - and then I get the warning, at which point I pause for a second and think: did I add layers, masks, etc. that I need in case this file is a tiny bit off?. 99% of the time, I just close without saving - but there is that tiny percent left where I think hmm... I did save that really complex selection that might come in handy - what the hell, I'll save it. So in case #1, it adds all of a second or maybe three to my workflow and I've become quite used to it. It seems the loudest complaints come from similar workflows - which are not part of GIMP's target. Which brings me to... 2.) Full-on GIMP - lossless editing - I'm creating a layered composition, or a background for another composition that is layered and/or complex. - So there's anything from text layers, layer masks, blending modes - all types of stuff that isn't going to be retained in the export format. - I work, save the file as eg file_20130615-01.xcf. I export in my target format. - If the final needs changes (or I've been working over an hour), I save as file_20130615-02.xcf, work, save, export. Case #2 is exactly how I work with everything in Adobe CS - Photoshop, Illustrator, etc. already. Except that eg Illustrator doesn't restrict the clean flag to just AI (it will treat PDF and EPS as a cleanly saved format), it's exactly the same behavior. For example if I create a file in AI, save it, make some changes, export PNG, close it - it will warn me that wait for it I didn't save the changes in a format that will be recognized by Illustrator the next time I open the file. Sounds familiar, no? ;) Since I already work this way, I never see the you didn't save dialog on these types of GIMP projects. At least, if I'm doing it right that is ;) So it adds 0 seconds to my workflow. I'll give you a simple example of #2: a client sends me a set of bracketed images of a property to combine as HDR (never mind that there are plenty of other tools, client also wants the dog poop out of the yard and the windows cleaned while we're at it, eh?). I'm certainly going to consider the file saved only when it retains all of my layers and masks, never mind if the client is only going to see the exported JPEG. That way, when they come back and ask now can we make the sky green? (stranger requests have been made), it's open, adjust layer, save as, export, close instead of open, make mask (again), adjust, export, close, don't save. Which saves me time, which saves them money, which makes me more valuable as an asset. If all of your GIMP usage falls into #1, you're probably using the wrong tool for the job. Either deal with the extra dialog, or deploy one of the various workarounds (or use another tool). If you're in #2, the distinction should make no difference at all, really, unless you enjoy doing the same work over and over again. Chris PS - we can do without the name-calling and nation-baiting. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, Jun 15, 2013 at 7:28 AM, Norbert Preining prein...@logic.at wrote: These bullying emails are just plain rubbish. Software should be written with the users in mind. And - opening a jpg file - editing - saving should result in a saved version of yhe original file, because that is what practically all programs are doing, and what the user expectation, and natural behaviour i Grue beat me to this, but this doesn't work for JPEG. If you have a text editor, you could create a document with say 1 header and 3 paragraphs. Then you could edit paragraph #1 a thousand times, save each time, and your header and other paragraphs remain identical. However if you edit a portion of a JPEG a thousand times, and save a thousand times, the whole of the image is going to take some major punishment. In this case instead of saving you are really reencoding. Would you consider your text document saved if random characters were transposed throughout? Chris ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 06/15/2013 01:53 PM, Grue wrote: Wow, just wow. Here are the facts: every time you save your image as JPEG, you lose information. It is by design a lossy image format that uses an algorithm to conserve your disk space via throwing away some insignificant information (which works well for photos, but ruins many other types of images). Worse yet, if you edit a JPEG image and resave it, you lose even more information. This results in very noticeable artifacts in the image. And GIMP actually tries to prevent you from this destructive workflow, yet you keep doing it anyway, and you're complaining about GIMP instead of your own ineptitude. Please, if you work with images, learn about image formats and how they work. The eyes of people who look at your images will thank you later. Well? It seems for all the reasons this Save As... behavior has been established, it's not working. Culture and expectations will out. Personally, I have gotten used to the change. It's still a bit of a tick with me but it reminds me the difference between a work file and a published output file... I remember it each and every time I edit an image. However... I don't feel any more professional than I did before. My workflow? Not quite as flowing as it is in other software which uses a consistent behavior. Inkscape, another program I use for image editing and creation, allows me to Save as... any supported image format just fine which is interesting because of the two programs, Inkscape would actually make more sense to have exhibit this behavior. And when I close the program afterward, I am prompted with: ''The file drawing.png was saved with a format (org.inkscape.output.svg.inkscape) that may cause data loss! Do you want to save this file as Inkscape SVG? [Close without saving] [Cancel] [Save as SVG]'' (This sort of reminds me of Smoking causes cancer labels.) The reason I say the GiMP behavior is more suited to Inkscape is that when using a program like Inkscape, a user is using a variety of primitive tools to compose an image which requires many, many steps and manipulations. But also, Inkscape has export functions such as save as copy and export bitmap. It allows me to do what I want to do, but then reminds me I might be making a big mistake if close the program without saving in the native format. This approach, Inkscape's that is, actually comes closer to accomplishing the purpose described by GiMP's developers without enraging the the user. Apologies all around... I realize this is a wasted effort... I've seen this conversation go on multiple times and I've even started and participated in one myself. But when I see an example of people doing what they want to do regardless of warnings and speed-bumps and preventative measures, it just goes to show you can't beat stupid and you can't force smart. A simple warning that you may be screwing something up is probably the best approach. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Rescale Tool - Layer Mask Added
Thanks, it is that's a very simple way, and is the way I currently work. I just thought the logically way would have been to scale a active masked layer as seen with the mask active. On 15/06/2013 20:29, Daniel Hauck wrote: Taking the obvious approach, I always just duplicate a layer and make it not visible. That way, I can use the copied layer again in other ways. Simple. On 06/15/2013 03:24 PM, Andrew Bridget wrote: When you try to rescale a layer using the Rescale Tool with a layer mask active, it scales of the mask, likewise if you select the layer it will scale the layer. Can I select both the layer and layer mask and scale the layer, thus it keeps the layer mask showing the desired masked area only. As the only way I can see currently is by applying the layer mask on the layer and then you can see the layer/s below to get the scaling that is desired. But I would like to keep the layer mask active for editing after scaling. Andrew ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ?
When you make an edit on the image and you export it, the JPEG doesn't disappear and the edited image still shows in the image window. It's that you want to see the _exported_ JPEG file to confirm the export resulted in the JPEG file you wanted to create for the client I think you're thinking you have to re-open the exported JPEG file in GIMP to make more edits is causing some confusion. Not exactly, no, the edited image that is now on my screen, the xcf, is probably a resolution of 300 x 300 and may be a print size of 12 x 16; But the exported image is a resolution of 72 and is not meant for printing. *That* is the one that I have to re-open (because I can't force it not to close when I export.) *That's* the one I have to mail, and if I decided to make a tweak, I can't just save and mail -- I have to export, re-open ... I don't see any way around the repeated reopenings except to make sure everything I do is perfect the first time, and that's even less likely than the developers reconsidering this. Thank you Tom. gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list -- Helen Etters using Linux, suse12.3 ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sat, Jun 15, 2013 at 4:01 PM, Alexandre Prokoudine alexandre.prokoud...@gmail.com wrote: On Sat, Jun 15, 2013 at 11:53 PM, Helen wrote: Here are the facts: every time you save your image as JPEG, you lose information. It is by design a lossy image format Exactly! We should not have to keep opening these files! They should stay on my screen until I finish with them. But noone's forcing you to close them. Are you kidding? When I export, it closes! If you know some way that I can keep my .png or .tif or .jpg open after saving it (aka exporting) in that format, please tell us how. It is the new GIMP that is forcing it to close! Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list -- Helen Etters using Linux, suse12.3 ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On Sun, Jun 16, 2013 at 12:14 AM, Helen wrote: Exactly! We should not have to keep opening these files! They should stay on my screen until I finish with them. But noone's forcing you to close them. Are you kidding? Nope. When I export, it closes! It shouldn't and it never did so for me. In fact, I don't think it ever did that for anybody. I don't see a single report like yours. There's something crazy going on with your computer and your copy of GIMP. What happens for just about everybody else is: 1. File Export 2. Specify file name 3. Click 'Export' 4. Contonue working on the picture. Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 06/15/2013 01:19 PM, Alexandre Prokoudine wrote: On Sun, Jun 16, 2013 at 12:14 AM, Helen wrote: Exactly! We should not have to keep opening these files! They should stay on my screen until I finish with them. But noone's forcing you to close them. Are you kidding? Nope. When I export, it closes! It shouldn't and it never did so for me. In fact, I don't think it ever did that for anybody. I don't see a single report like yours. There's something crazy going on with your computer and your copy of GIMP. What happens for just about everybody else is: 1. File Export 2. Specify file name 3. Click 'Export' 4. Contonue working on the picture. Alexandre Prokoudine http://libregraphicsworld.org ___ I'm thinking Helen is referring to the JPEG preview window that opens, during the JPEG export process.After the JPEG export is done, the preview window closes since the file's been saved. Peace... Tom -- /When we dance, you have a way with me, Stay with me... Sway with me.../ ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
Tom Williams (tomd...@comcast.net) wrote: I'm thinking Helen is referring to the JPEG preview window that opens, during the JPEG export process.After the JPEG export is done, the preview window closes since the file's been saved. However, the separate window only shows up when one is working in indexed mode. Which is not what you're doing when you started by opening a JPEG... Not sure what is going on there. Bye, Simon -- si...@budig.de http://simon.budig.de/ ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A Sad case of regression
On 15.06.2013 22:21, Tom Williams wrote: On 06/15/2013 01:19 PM, Alexandre Prokoudine wrote: There's something crazy going on with your computer and your copy of GIMP. What happens for just about everybody else is: 1. File Export 2. Specify file name 3. Click 'Export' 4. Contonue working on the picture. I'm thinking Helen is referring to the JPEG preview window that opens, during the JPEG export process.After the JPEG export is done, the preview window closes since the file's been saved. That behavior isn't different to previous versions, though... -- Regards, Michael ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Technical issues with recent mails (was: Re: A sad case of regression ?)
I'd noticed the broken threading too and saw this from . = David Russel No less than six digests were waiting to be read this morning, almost entirely cluttered with this nonsense. I think that explains why every message from him starts a new thread (also with subtlety different subject lines). At least he edits his subject so that it doesn't read Re:[Gimp-user] Digest . I don't know any way to maintain threading when participants are receiving digests and this is why I always request individual emails. GMail does a slightly better job of keeping things together but it shows 5 threads with respectively 9, 1 (this one), 32, 25 and 18 each. Regards ... Alec (buralex@gmail WinLiveMess - alec.m.burgess@skype) On 2013-06-15 08:34, Michael Schumacher wrote: I'd like to point of some issues with a few of the recent mails: 1. Broken threading Some users apparently reply with mail software which breaks threads, e.g. does not add In-Reply-To: / References: headers to sent messages. This starts a new thread for that message. Users 'Crew' and '.', please check your application settings and ensure that replies are threaded properly. The latter user is also advised to change the name part of the mail address, in order to not be caught by many spam filters. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ?
Date: Sat, 15 Jun 2013 16:12:06 -0400 From: etter...@gmail.com To: tomd...@comcast.net CC: gimp-user-list@gnome.org Subject: Re: [Gimp-user] A sad case of regression ? Not exactly, no, the edited image that is now on my screen, the xcf, is probably a resolution of 300 x 300 and may be a print size of 12 x 16; But the exported image is a resolution of 72 and is not meant for printing. *That* is the one that I have to re-open (because I can't force it not to close when I export.) *That's* the one I have to mail, and if I decided to make a tweak, I can't just save and mail -- I have to export, re-open ... I don't see any way around the repeated reopenings except to make sure everything I do is perfect the first time, and that's even less likely than the developers reconsidering this. Thank you Tom. I'm not making any sense of this at all. Image resolution is a piece of metadata and does not in any way dictate the size of the image as measured in actual image pixels. If you open an image whose tags say 300 dpi, when you save (or export) it the output file will contain that 300dpi setting. Now if the image is 12x16 and tagged as 300dpi this means that the image's physical PIXEL dimensions are 3600x4800. And when you export this image to a JPG, that JPG will still be be 3600x4800 pixels large (and tagged as 300dpi) unless you specifically dictated to GIMP otherwise. Going to the Image menu and selecting Resize image... rescales the image to a different size in pixels (but doesn't necessarily change the dpi metadata); selecting Print Size... lets you set the dpi metadata directly, but doesn't change the pixel content of the image. Also, when you export the image to a JPEG, if suddenly your open image window disappears, well that is not supposed to happen at all and sounds something like a GIMP program crash, but we don't have enough information as is to determine that. And when GIMP crashes, you at least get a message telling you in no ambiguous terms that something crashed. -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ?
On Fri, 2013-06-14 at 22:37 -0400, Helen wrote: The export feature could have been added without disabling the save as feature. Control-shift-e (export to) works like the old save as for non-xcf formats. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ? [saving undo history]
On 06/16/2013 11:38 AM, Liam R E Quin wrote: On Sat, 2013-06-15 at 08:03 -0700, Richard Gitschlag wrote: Date: Sat, 15 Jun 2013 11:30:43 +0200 From: schum...@gmx.de To: gimp-user-list@gnome.org Subject: Re: [Gimp-user] A sad case of regression ? . . . That's not perfect yet - for example, you lose the undo history . . . How often is Undo history ACTUALLY needed by the user, beyond fixing a ten-seconds-ago mistake? I can't personally name a single application that stores undo history with the document's workfile; but if you can, let me know. no-one swims across the river here so we don't need a bridge? I've used commercial software that stored editing history in a database - you can go back through the entire history of most aircraft manuals and see all the edits, for example, for obvious legal reasons. I've many times wished I could save undo history - e.g. I'm experimenting, but my flight is boarding or my battery is low. Liam Think about it. Undo history can actually save some users the hassle of an overlooked mistake. It's there quietly sitting in the corner not really berating the workflow. It's not like it's really affecting a smooth workflow. Archie ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] A sad case of regression ?
On Sun, Jun 16, 2013 at 12:12 AM, Helen wrote: don't see any way around the repeated reopenings Mmm... There's this difficult to catch bug... Sometimes when there are multiple images opened in the single-window mode, exporting an image that's among the first tabs to the left results in GIMP jumping to the last opened image (rightmost tab). That _could_ give an impression that GIMP closes an image. Is that what's happening? Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
