[Gimp-developer] CIE-LCH Color selector?
Hello, The last discussion about using CIE LCH for some layer modes made me remember that there is a CIE LCH color selector plugin for GIMP that many people would like to see included in the main GIMP distribution sooner or later. It has room for improvements (for example when colors out of gamut are selected it can lead to some strange color selection results), but it should be a good start to begin from. Of course there is the source code available, and it's public domain too, according to the author. I've attached the tar.gz file to this email. -- SHIRAKAWA Akira gimp-lch-selector-0.3.tar.gz Description: application/gzip ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] XMPModel and custom signals
Hi Martin, On Sun, Aug 02, 2009 at 01:58:20PM +0200, Martin Nordholts wrote: On 08/02/2009 01:50 PM, Roman Joost wrote: does not change the fact that it would be nice to have a 'property-changed' signal as a convenience if you have the need to listen property changes So ... I'm just wondering. If I like to use two signals for the XMPModel, does it still make sense to inherit from GtkTreeStore? I mean, I can't currently see any benefits if I inherit from GtkTreeStore. In general, aggregation is preferable to inheritance because the former results in more dynamic code with less assumptions. If you think aggregation makes more sense than inheritance in this case, then I'd say go ahead and use aggregation, i.e. have a GtkTreeStore as an instance member in XMPModel Should I redo the patch posted for the bug I've created at: http://bugzilla.gnome.org/show_bug.cgi?id=589474 and implement the schema change signal (which is missing), or can someone review the patch again? Cheers, -- Roman Joost www: http://www.romanofski.de email: romanof...@gimp.org signature.asc Description: Digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CIE-LCH Color selector?
On 08/03/2009 10:45 AM, SHIRAKAWA Akira wrote: Hello, The last discussion about using CIE LCH for some layer modes made me remember that there is a CIE LCH color selector plugin for GIMP that many people would like to see included in the main GIMP distribution sooner or later. Before we add support for picking device-independent colors, the whole color selector should be color managed, and it currently isn't. I'm all for adding a Lab/LCH color picker when that is fixed though. / Martin -- My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CIE-LCH Color selector?
Martin Nordholts wrote: Before we add support for picking device-independent colors, the whole color selector should be color managed, and it currently isn't. I'm all for adding a Lab/LCH color picker when that is fixed though. Ah, I see, thanks anyway for checking it out. By the way, as I wrote in another message I'm not a GIMP hacker, but by not color managed did you refer to this specific implementation of a LCH color picker or rather the whole GIMP color picking system? -- SHIRAKAWA Akira ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CIE-LCH Color selector?
On 08/03/2009 05:07 PM, SHIRAKAWA Akira wrote: Martin Nordholts wrote: Before we add support for picking device-independent colors, the whole color selector should be color managed, and it currently isn't. by not color managed did you refer to this specific implementation of a LCH color picker or rather the whole GIMP color picking system? I'm referring to the whole GIMP color picking system. The color picked using the default color picker is not represented in a device-independent way. One of the consequences is that painting with a green brush on a color managed image might not give a green stroke on the image. The absence of a color managed color picker becomes evident in test images which rotates color, i.e. maps e.g. RGB 0,255,0 in the image to RGB 0,0,255 on the screen. / Martin -- My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CIE-LCH Color selector?
Martin Nordholts wrote: I'm referring to the whole GIMP color picking system. The color picked using the default color picker is not represented in a device-independent way. One of the consequences is that painting with a green brush on a color managed image might not give a green stroke on the image. The absence of a color managed color picker becomes evident in test images which rotates color, i.e. maps e.g. RGB 0,255,0 in the image to RGB 0,0,255 on the screen. I understand, thanks for explaining. Can you give a rough estimate of when a color managed picking system will be integrated into GIMP ? I've only recently discovered the LCH color space / color selection and I think it's a great system. I know I could for now simply use the current available color selection module (which from what I see is just a graphic interface to do LCH-RGB24 color conversions, so it's a sort of fake LCH), but it's just my curiosity. Let me guess: this will happen when GEGL will be fully integrated into GIMP, right (also allowing higher color bit depths which if I'm not wrong the LCH color space needs) ? Then that would be in GIMP 2.10 or even later, I think. -- SHIRAKAWA Akira ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CIE-LCH Color selector?
On 08/03/2009 05:44 PM, SHIRAKAWA Akira wrote: Can you give a rough estimate of when a color managed picking system will be integrated into GIMP ? Making the color picker color managed has not been incorporated in any short or long term plan yet. So yeah, maybe we will get around to do it in GIMP 2.10 which has big changes scheduled already. / Martin -- My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
Hi, On Sat, 2009-07-25 at 17:41 +, Omari Stephens wrote: More specifically, once I hit Ctrl+E and see the status message not saying anything about exporting, I expect the file to have been saved. If GIMP thinks there were no changes, it should say no changes to save in a way that is visible, easy to notice, and easy to read. It does exactly that. It will display the text No changes need to be saved in the status-bar and this text stays there for five seconds unless it is replaced by a more important status-bar message before this timeout expires. If that doesn't happen for you, then this code broke and there should be a bug report filed. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On Monday 03 August 2009 22:20:29 Sven Neumann wrote: On Sat, 2009-07-25 at 17:41 +, Omari Stephens wrote: More specifically, once I hit Ctrl+E and see the status message not saying anything about exporting, I expect the file to have been saved. If GIMP thinks there were no changes, it should say no changes to save in a way that is visible, easy to notice, and easy to read. It does exactly that. It will display the text No changes need to be saved in the status-bar and this text stays there for five seconds unless it is replaced by a more important status-bar message before this timeout expires. If that doesn't happen for you, then this code broke and there should be a bug report filed. Why only 5 seconds? why not until something else happens? IMHO 5 seconds is not enough. --Alexia ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] What would be a better set of default resources?
Hi, On Fri, 2009-07-24 at 13:10 +0200, Martin Nordholts wrote: What is the migration time? You would have to deal with this on each and every start of GIMP. System resources may have changed, due to a minor or micro GIMP update or because the system maintainer added or removed resource files. This cannot be handled easily if we follow your approach and the result is a total mess. We don't need to handle this. We don't need to adapt GIMP to a typical multi-user environment found at universities for example because those are not our target audience. Handling this at user dir migration to a new version is fine. Of course we need to keep such multi-user environments in mind, even if they are not our main target. And apart from that, you get the same situation if the user herself installs an extra data package for GIMP system-wide by means of the packet management system of her Linux distro. * We would have to treat editing of normal resources and read-only resources differently Sure, but that is rather simple. Just make a copy and auto-hide the read-only resource. * When editing a read-only resource we would have to mark the read-only resource as deleted to give the user the impression that it was the read-only resource he edited See above. You are using your arguments multiple times. These are not arguments, they are example of where we need to add special cases. The more of these, the bigger the mess. That the special cases all stem from the same design approach is not relevant. Right, these are special cases and their number is important. Which is why I pointed out that you are using the same example multiple times only to increase the number of special cases. That is not a fair comparison, I am afraid. GIMP has done it the way you proposed in the past and copied system resources to the user directory. This was ugly and caused lots of grief. Eventually we got rid of this mess and now you are proposing to undo this work and to reintroduce this ugliness? That's very disappointing. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] What would be a better set of default resources?
On 08/03/2009 09:33 PM, Sven Neumann wrote: GIMP has done it the way you proposed in the past and copied system resources to the user directory. This was ugly and caused lots of grief. Eventually we got rid of this mess and now you are proposing to undo this work and to reintroduce this ugliness? That's very disappointing. I later realized that I was attacking the problem in the wrong way, it's not about making our current brush system work, it's about designing a completely new system. With this in mind, copying system resources to the user dir at user dir instantiation is not attractive to me any longer. BR, Martin -- My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] XMPModel and custom signals
Hi, On Fri, 2009-07-31 at 15:12 +1000, Roman Joost wrote: I could and the patch provided by that bug adds a custom 'property-changed' signal. Sven and Mitch thought, if I inherit from XMPModel, I wouldn't really need the 'property-changed' signal, because I'd be able to control the 'property-changed' signal. That is true, but maybe I wasn't clear enough saying, that I want to distinguish if a schema or a property changed by using different signals. Nothing keeps you from adding more signals to your derived class. You can easily emit more detailed signals from the 'row_changed' handler in your class. What's probably even better than a plain 'property-changed' signal is one that has a detail that identifies the property. Then code can subscribe to 'property-changed' to get notified about any property changes and your entry, which is probably just interested in a special property, let's call it 'foo', would subscribe to 'property-changed::foo'. See http://library.gnome.org/devel/gobject/stable/signal.html#signal-detail for more information on the detail argument. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On 08/03/2009 03:28 PM, Alexia Death wrote: On Monday 03 August 2009 22:20:29 Sven Neumann wrote: On Sat, 2009-07-25 at 17:41 +, Omari Stephens wrote: More specifically, once I hit Ctrl+E and see the status message not saying anything about exporting, I expect the file to have been saved. If GIMP thinks there were no changes, it should say no changes to save in a way that is visible, easy to notice, and easy to read. It does exactly that. It will display the text No changes need to be saved in the status-bar and this text stays there for five seconds unless it is replaced by a more important status-bar message before this timeout expires. If that doesn't happen for you, then this code broke and there should be a bug report filed. Why only 5 seconds? why not until something else happens? IMHO 5 seconds is not enough. --Alexia Alexia, One of my annoyances with a couple of other programs that I use a lot is that such types of messages stay around too long in those programs. What if you look at the screen 30 seconds or 5 minutes or 2 hours later that message is still there? It is now completely out of context! While maybe 5 seconds might be a little quick, conceptually I agree that it should not last very long. Maybe 8 or 10 seconds or even 15 seconds. But not longer. Jay ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
Hi, On Mon, 2009-08-03 at 15:51 -0400, Jay Smith wrote: While maybe 5 seconds might be a little quick, conceptually I agree that it should not last very long. Maybe 8 or 10 seconds or even 15 seconds. But not longer. Maybe five seconds is indeed somewhat short. Would anyone object if we increased this to ten seconds? If someone wants to try it, the timeout is defined at the top of app/display/gimpstatusbar.c. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
Sven Neumann wrote: Hi, On Mon, 2009-08-03 at 15:51 -0400, Jay Smith wrote: While maybe 5 seconds might be a little quick, conceptually I agree that it should not last very long. Maybe 8 or 10 seconds or even 15 seconds. But not longer. Maybe five seconds is indeed somewhat short. Would anyone object if we increased this to ten seconds? If someone wants to try it, the timeout is defined at the top of app/display/gimpstatusbar.c. Sven I found I had bearly noticed the presence of the message and definately did not have time to read it. I think what actually caught my eye was the fact it disappeared whilst I was looking around wondering why I was not getting the usual progress bar I was expecting. I stress, the reason I knew something was wrong was that the save was too quick , not that the message caught my eye. 10s may help but IMHO this method of notification is far too unobtrusive. The STATUS bar should be for relaying status information. Information that relates to the state of the program. It is used effectively to prompt awareness of hot key combinations etc. This is accessory information that the user may check for or that my just be helpful. The text is small and on the periphery of vision when the focus of attention is on the centre of the screen. It is NOT an effective way of displaying important error messages that NEED to be seen. As I said in my original post , this is not a by the way the image was not saved it is an error condition what warrants an modal dialogue and a user response. If the error is irrelevant then the current mechanism is probably OK. I maintain that it is non trivial and requires full visibility. /gg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On 08/03/2009 05:04 PM, gg wrote: snip lots It is NOT an effective way of displaying important error messages that NEED to be seen. As I said in my original post , this is not a by the way the image was not saved it is an error condition what warrants an modal dialogue and a user response. If the error is irrelevant then the current mechanism is probably OK. I maintain that it is non trivial and requires full visibility. /gg I second this motion (or emotion). I would rather have to dismiss a dialog box than to think I have saved something that has not been saved. Jay ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On 08/03/2009 11:04 PM, gg wrote: As I said in my original post , this is not a by the way the image was not saved it is an error condition what warrants an modal dialogue and a user response. Please let's not bombard the UI with modal dialogs. They are excellent for interrupting workflows and annoying users. The proper solution is to make changing the comment dirty the image, it is not to show a modal dialog when the image is not saved. / Martin ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On 08/03/2009 05:12 PM, Martin Nordholts wrote: On 08/03/2009 11:04 PM, gg wrote: As I said in my original post , this is not a by the way the image was not saved it is an error condition what warrants an modal dialogue and a user response. Please let's not bombard the UI with modal dialogs. They are excellent for interrupting workflows and annoying users. The proper solution is to make changing the comment dirty the image, it is not to show a modal dialog when the image is not saved. / Martin Martin, I appreciate your thinking on this and what you suggest in this particular situation is a great way to deal with that specific case. However, I would like to point out that if a user _intends_ to save the file because the _user_ believes a change has been made, then should not the user be notified that either a) the user is incorrect and no change has actually been made [and thus the user probably needs to do something that the user has failed to realize has not been done], thus the file is not going to be saved OR b) the program is incorrect in thinking that no change has been made (as was the case in this situation). _I_ would want my workflow interrupted if the program was not going to do what I had asked it to do. Maybe that's just me. As long as the focus in the modal dialog is on the dismiss button, then it is easy enough to hit [Enter] and it goes away. That would be my preference. Jay ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On 08/03/2009 11:19 PM, Jay Smith wrote: _I_ would want my workflow interrupted if the program was not going to do what I had asked it to do. Maybe that's just me. Hi Jay When you do a File - Save you want to make sure that your changes is safely written to disk, right? If you have made no changes, what is then the point in writing the file again? The user should be able to trust that GIMP does the right thing and it is unfortunate whenever GIMP doesn't. But showing a modal dialog whenever the user presses Ctrl+S twice is to me a really bad idea UI-wise. Regards, Martin -- My GIMP Blog: http://www.chromecode.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On Mon, Aug 3, 2009 at 3:51 PM, Jay Smithj...@jaysmith.com wrote: On 08/03/2009 03:28 PM, Alexia Death wrote: Why only 5 seconds? why not until something else happens? IMHO 5 seconds is not enough. One of my annoyances with a couple of other programs that I use a lot is that such types of messages stay around too long in those programs. What if you look at the screen 30 seconds or 5 minutes or 2 hours later that message is still there? It is now completely out of context! I disagree. If the last thing I did that generates such a message was try to save, then even 2 hours from now it still has THAT context (that is, the last thing you did). Keeping the message in the status bar until it is replaced is, imho, the minimum possible solution to this problem. I, like some others in this thread, would prefer a modal dialog. On Mon, Aug 3, 2009 at 5:27 PM, Martin Nordholtsense...@gmail.com wrote: When you do a File - Save you want to make sure that your changes is safely written to disk, right? If you have made no changes, what is then the point in writing the file again? The user should be able to trust that GIMP does the right thing and it is unfortunate whenever GIMP doesn't. But showing a modal dialog whenever the user presses Ctrl+S twice is to me a really bad idea UI-wise. Maybe I just want to 'touch' the file and saving is the fastest possible way to do that. Perhaps I modified or deleted the file on disk, and want to save the copy that exists in GIMP over whatever is on the disk. I am not sure if GIMP is already aware of this situation In some situations, the Save operation produces dialogs from the export plugin, which do not affect the image in GIMP but do affect the saved image. What if I just want to change the decisions that I made there? (again, this may already be handled well). ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
Martin Nordholts wrote: On 08/03/2009 11:19 PM, Jay Smith wrote: _I_ would want my workflow interrupted if the program was not going to do what I had asked it to do. Maybe that's just me. Hi Jay When you do a File - Save you want to make sure that your changes is safely written to disk, right? If you have made no changes, what is then the point in writing the file again? The user should be able to trust that GIMP does the right thing and it is unfortunate whenever GIMP doesn't. But showing a modal dialog whenever the user presses Ctrl+S twice is to me a really bad idea UI-wise. Regards, Martin Martin, I completely agree that is good not to have unnecessary dialogues and appreciate the work that Peter and others have done in that direction , but Jay sums up well the points I originally made. I generally know when I have not made at least one change. I do not blindly hit cntl_S every 30s just in case. If I save a saved image I'm probably making a mistake and I want to know about it. Maybe the mouse is not over the window I think or the window I'm looking at is not the current one I have altered . Again I am mistaken and need to know. When we can close down bugzilla because gimp no longer has any bugs , your argument about trusting gimp will have more weight. The minor bug I picked up here proves it is too soon to apply that rationale. This feature (unobtrusive messaging) may well be useful in an auto save situation . This may even be the reason it was done this way. In that case I would suggest adding a means for auto save to have an execution path that does not produce unneeded save operations nor warn about the condition. My contention here only applies to a direct user action. regards. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
gg wrote: ... much erudition elided... 10s may help but IMHO this method of notification is far too unobtrusive. The STATUS bar should be for relaying status information. Information that relates to the state of the program. It is used effectively to prompt awareness of hot key combinations etc. This is accessory information that the user may check for or that my just be helpful. The text is small and on the periphery of vision when the focus of attention is on the centre of the screen. It is NOT an effective way of displaying important error messages that NEED to be seen. It's right in line with good UI practice. This message is not status, it's an error report and should be displayed in a way such that the user HAS to deal with it before moving on. What they asked for didn't happen and they must know. A modal dialog is an example of how to deal with this, a disappearing status message is not. Patrick ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
Sparr wrote: Maybe I just want to 'touch' the file and saving is the fastest possible way to do that. Perhaps I modified or deleted the file on disk, and want to save the copy that exists in GIMP over whatever is on the disk. I am not sure if GIMP is already aware of this situation Valid point. If I am trying to save to recover a deleted file this becomes a data loss scenario. In some situations, the Save operation produces dialogs from the export plugin, which do not affect the image in GIMP but do affect the saved image. What if I just want to change the decisions that I made there? (again, this may already be handled well). In the same way that I had to make a small edit to save the comment because of the parasite bug, if I want to resave a jpeg with various compression ratios until I get a suitable result , I would presumably have to Save As... to serval new files and clean up with a file manager later. When I have to start looking for work arounds like this , the interface is trying to be too clever. Let me drive ! /gg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Bug #164774
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://bugzilla.gnome.org/show_bug.cgi?id=164774 Hi - I was going to look into this enhancement. It was a request to make it possible for the user to change the zero-point of the image rulers. However, it looks like the last comment was made about three years ago. Since I'm new around here, I was wondering if there had been any relevant discussion on the issue recently. (Or related discussion.) - -- http://indicium.us http://theologia.indicium.us I sign /all/ my e-mail messages via PGP. If you receive any e-mail supposedly from me without my valid PGP digital signature, please take additional steps to verify the authenticity of the message. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkp3ctcACgkQQ5FLNdi0BcXwwQCfXxgbehH1n/3XbBNzS1X0y2e/ 4YoAn1BakhDbMI65yYGCkRv9b1QjiFUz =XYSb -END PGP SIGNATURE- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On Mon, Aug 3, 2009 at 5:12 PM, Martin Nordholts ense...@gmail.com wrote: Please let's not bombard the UI with modal dialogs. They are excellent for interrupting workflows and annoying users. The proper solution is to make changing the comment dirty the image, it is not to show a modal While I agree, what about the idea of an 'elevated status' message appearing in a toaster? If you think of how some IM clients notify, this 'elevated status' message could pop up from the status bar. It would stay open for 10-15 seconds and then disappear back into the status bar. There could be a small red 'X' in the upper right to dismiss the message immediately, otherwise it remains non-modal. Clicking the message itself could pull up the appropriate section of the GIMP help manual (or something else useful). Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] cant save image with new comment
On Mon, 2009-08-03 at 22:06 -0400, Christopher Curtis wrote: [...] If you think of how some IM clients notify, this 'elevated status' message could pop up from the status bar. It would stay open for 10-15 seconds and then disappear back into the status bar. So I press save, and go for a coffee, and come back confident my file was saved, knowing that I'd get huge alarm bells ringing if the operation failed. And your elevated status message would be as long gone as Sven's much less irritating but basically invisible status bar message. Please, if I go to overwrite another file, I get a big warning, and I want that. If I try to save and it doesn't work, I want a warning too. A clear warning not just that one of the gargoyles on the gate-posts fluttered one eyelid in the dark when no-one was watching. Make me press OK :-) Even if I had previously saved to the same location, GIMP is surely not checking things like the USB device ID on a remote network drive, and has no idea I changed the thumb drive. Thanks ;) -- 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 www.advogato.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
