Re: [Gimp-developer] Unplugging Wacom crashes GIMP
On Wed, Aug 5, 2009 at 12:26 AM, Patrick Horgan wrote: > > 1) If I plug it in after the gimp is already started it isn't recognized > as a tablet, i.e. doesn't appear as an extended input device that can be > configured and works only as a mouse. > 2) If I plug it in before starting the gimp, it's recognized and works > well, but if I unplug it before exiting the gimp, gimp will crash in a > little bit. > > Inkscape has exactly the same behavior including the crash. This is a known issue, and exists because there is no agreed interface for X to tell applications about appearing and disapearing devices(there is DBUS, but im not sure if X sends the type notifications needed for this use) and no mechanism in the toolkits(in this case, GTK) to handle it, because its rather new for X to have appearing and disapearing input devices. Gimp sees what devices are available on startup and wont be aware of the devices added later. When you remove a device however, gimp(or rather GTK IIRC) will try to get data from a noinexisting device and crash. I quickly looked at the issue when I encountered it myself and it was quite above ma capabilities to fix, but I dont remember the details any more. -- --Alexia P.S Sorry for the spam, Patrick. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Bug #164774
Martin Nordholts wrote: > There hasn't been any further discussion, but we should have one. The > first step would be to figure out a UI for the feature that helps > fulfill the product vision [1]. As left clicking and dragging with the mouse creates new freely movable guides (left click-drag the upper ruler for horizontal guides, left click-drag the left ruler for vertical guides), I suggest that clicking and dragging the rulers (left-right for the upper one, up-down for the vertical one) with another mouse button (for example middle or right) could move their respective origin (zero point). Then, another option in the "Image" menu and below "Configure Guides...", called "Configure Rulers...", could be added for more precise ruler option settings (I was thinking not only the origin, but also font, style, number of notches, etc, if it's possible). But this is just my 2-minutes brainstorm. -- SHIRAKAWA Akira ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Bug #164774
On 08/04/2009 01:29 AM, Christopher Howard wrote: > -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.) Hi, There hasn't been any further discussion, but we should have one. The first step would be to figure out a UI for the feature that helps fulfill the product vision [1]. BR, Martin [1] http://gui.gimp.org/index.php/GIMP_UI_Redesign#product_vision -- 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 Wed, 2009-08-05 at 00:06 +0200, gg wrote: > Martin Nordholts wrote: [...] > I think not saving has merit for large files (especially long png > compression) on condition this is clearly put to the user. As Sven said, there are separate issues - (1) gimp doesn't always know the user's intention. Better to save asked to do so. (2) changing the comment should mark the image as dirty, of course (3) if for some reason the user presses save and nothing happens, a clear message is needed. Making "save" insensitive is OK too I think, and is what most other programs do in this case. But, if GIMP is primarily catering to the "power user", it should go ahead and save, and not try to out-guess anyone. The changes to file save/export help in some ways, and not in others: it's now necessary for the user to keep track of three separate images and their state -- the "precious original", the image in gimp, and the file to which you're exporting the result of your work so you can use it. I'd really like to see an indication in the undo history (even though it's not an undoable step) of when you saved or exported, and where. Making the status easier to see would reduce the chance a "power user" accidentally tries to save an unchanged image and has to wait. Liam PS: in case it wasn't clear, I'm not accusing anyone of trying to hide anything :-) -- 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
Re: [Gimp-developer] XMPModel and custom signals
On Mon, Aug 03, 2009 at 09:46:34PM +0200, Sven Neumann wrote: > 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. Wow - awesome. That looks very much I'd like to use. I revamp the XMPModel and try to incorporate this for the property-changed signal. Thank you both, Martin and Sven. 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] cant save image with new comment
Martin Nordholts wrote: > On 08/04/2009 08:27 PM, Sven Neumann wrote: >> Well, there have been some good arguments brought up in this thread why >> saving a clean image may make sense. So perhaps we should change the >> default for 'trust-dirty-flag' back to 'no' and always save the image? > > I was about to propose changing the default back to "no" too > > / Martin I think that is a good short term solution since it can be done with trivial effort. Although for the next cycle, a more rigourous solution could be better. I think not saving has merit for large files (especially long png compression) on condition this is clearly put to the user. I'd suggest a modal "trust me, do it anyway " vs "OK, forget it" choice that could avoid 30s saves at the expense of one click. The reasons have now been well covered. Once such a solution is found (and the parasite bug fixed) trust-dirty could be back on. I have opened a bug about the comment parasite not being detected. http://bugzilla.gnome.org/show_bug.cgi?id=590782 /gg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Unplugging Wacom crashes GIMP
Just checking to see if this is a gimp bug or whether I should look somewhere else. I'm using 2.6.6 on Ubuntu Ibex Linux dell 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 i686 GNU/Linux I switched from having the wacom device set up in xorg.conf to having a configuration in /etc/hal/fdi/policy/custom_wacom.fdi (attached). I did this so I'd get plug and play, i.e. not have to restart X when I plugged in my tablet. That has worked fine. There's just two different problems. 1) If I plug it in after the gimp is already started it isn't recognized as a tablet, i.e. doesn't appear as an extended input device that can be configured and works only as a mouse. 2) If I plug it in before starting the gimp, it's recognized and works well, but if I unplug it before exiting the gimp, gimp will crash in a little bit. Inkscape has exactly the same behavior including the crash. 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
Hi, On Tue, 2009-08-04 at 12:17 -0700, bgw wrote: > This thread is confusing me a bit. I have an xcf that I use to > generate png images for > a website. If I open the xcf, modify it, then save as png, and then > quit, the change to > the xcf is lost with no warning or, as far as I can see, any status > message. I'm using > 2.6.6-6.fc11.x86-64. Is this not a failure because I saved the png? That's another thing. And we believe that we fixed this long-standing confusion in the development branch by making Save always save to XCF. You now need to explicitly export your image to PNG and this operation does not clear the 'dirty' state. But yeah, this thread is confusing. Instead of filing a bug report about the fact that changing a comment does not mark the image as dirty, people have started to accuse GIMP (and its developers) of hiding important messages from the user. The real problem here is a bug and it still doesn't have a bug report even though lots of people found the time to contribute to this thread. Another problem is that the default for the 'trust-dirty-flag' property is perhaps not that well chosen. On the other hand, we changed this before GIMP 2.6 and it took like a year before the first complaint came in. So it appears to have worked quite well for most people... I am still convinced that it would be better to change the default back to 'no'. 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/04/2009 11:12 AM, Sven Neumann wrote: Hi, On Mon, 2009-08-03 at 22:25 -0400, Liam R E Quin wrote: 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. We are not talking about a save failure here. An image w/o changes does not need to be saved. So there is no failure here. This thread is confusing me a bit. I have an xcf that I use to generate png images for a website. If I open the xcf, modify it, then save as png, and then quit, the change to the xcf is lost with no warning or, as far as I can see, any status message. I'm using 2.6.6-6.fc11.x86-64. Is this not a failure because I saved the png? We could make the Save action insensitive for an image that is not dirty, then it would be more obvious that it won't do anything. 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. It doesn't even look at the file on disk. It just checks the image's dirty flag. If you dislike that behavior, there's the 'trust-dirty-flag' option that you can turn off. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer ___ 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 Tue, Aug 4, 2009 at 2:12 PM, Sven Neumann wrote: > We are not talking about a save failure here. An image w/o changes does > not need to be saved. So there is no failure here. I believe this has been thoroughly contradicted in this thread already. ___ 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/04/2009 08:27 PM, Sven Neumann wrote: > Well, there have been some good arguments brought up in this thread why > saving a clean image may make sense. So perhaps we should change the > default for 'trust-dirty-flag' back to 'no' and always save the image? I was about to propose changing the default back to "no" too / 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
Hi, On Tue, 2009-08-04 at 21:18 +0300, Alexia Death wrote: > > We are not talking about a save failure here. An image w/o changes does > > not need to be saved. So there is no failure here. > > > > We could make the Save action insensitive for an image that is not > > dirty, then it would be more obvious that it won't do anything. > > Actually that would be most sensible imho, if 'trust-dirty-flag' is set. Well, there have been some good arguments brought up in this thread why saving a clean image may make sense. So perhaps we should change the default for 'trust-dirty-flag' back to 'no' and always save the image? 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 Tuesday 04 August 2009 21:12:27 Sven Neumann wrote: > Hi, > > On Mon, 2009-08-03 at 22:25 -0400, Liam R E Quin wrote: > > 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. > > We are not talking about a save failure here. An image w/o changes does > not need to be saved. So there is no failure here. > > We could make the Save action insensitive for an image that is not > dirty, then it would be more obvious that it won't do anything. Actually that would be most sensible imho, if 'trust-dirty-flag' is set. --Alexia ___ 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 23:04 +0200, gg wrote: > 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. Important error messages are not displayed in the status-bar. Only messages of level INFO will be displayed in the status-bar. For more important messages we are using dialogs currently. It would be nice if we could instead have an area displayed at the top of the canvas, similar to what firefox is doing. Fortunately a widget for this has recently been added to GTK+. So it should be easier to get this done in the next development cycle when we can depend on GTK+ 2.18. 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
Hi, On Mon, 2009-08-03 at 22:25 -0400, Liam R E Quin wrote: > 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. We are not talking about a save failure here. An image w/o changes does not need to be saved. So there is no failure here. We could make the Save action insensitive for an image that is not dirty, then it would be more obvious that it won't do anything. > 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. It doesn't even look at the file on disk. It just checks the image's dirty flag. If you dislike that behavior, there's the 'trust-dirty-flag' option that you can turn off. 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
Liam R E Quin wrote: > 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. How about only starting the timer after the user proceeds to work on the image (drawing, selecting, running a filter, etc.)? (I really like the browser info bars Firefox utilizes for quick find or for asking whether to remember a password - I believe the latter actually stays around until you navigate away from the current page, which would be similar to my "until the user works on the image"...) -- Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria ...It might be written "Mindfuck", but it's spelt "L-A-I-N"... np: Orbital - Lush 3 (2Orbital (Disc 1)) ___ 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
> While maybe 5 seconds might be a little quick, conceptually I agree that >> it should not last very long. Please consider then, in particolar on Windows OS messages are often hidden behind the image windows. So a 5, 10, 0r even 15 second message will likely never be seen, and user will simply freak out later when he will see his work went lost If something go wrong when saving i pretend to know, this is a absolute priority, and i prefer be forced lose few second to close manually a unnecessary warning that lost beyond hope hours of work... May be only very few relevant warning...something as "SAVE FAIL" can't afford the risk to be ignored, because in that 10 second i was distracted by a phone call or because warning was hidden by another windows. And here as no relevance if the message was hidden for a Bug of Windows OS or for a Gimp bug...if there is the minimum risk that the message (a SIMILAR MESSAGE not in general )could be unnoticed then better be forced to manually close it before proceed. At least offer this as User option, please ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
