GNOME Bugzilla – Bug 326450
status bar while selecting should only count actual parts of the image
Last modified: 2008-01-15 13:03:55 UTC
Here is the scenario: I want to select the top of an image, all the way across. I probably want about 100px, but it also depends on how it looks. Here is what I try to do: * enlarge the window so the image has grey space around it * begin the selection on the grey area to the top left of the image * drag over the image * look at the status bar and see when it gets to 100. At that point, I might decide I want a bit more or a bit less. However, the status bar counts the pixels of the grey area outside the image. I don't see how to use GIMP to do what I want to do.
Right, that should be fixed at some point.
Sven, I hardly think it's 'minor'. I simply can't use GIMP to do this, and it's something I often find I need to do, alogn with making constained selections that touch a border.
I disagree. IMHO this is not even a bug. The numbers should display the size of the livewire you see on screen, not of the resulting selection. What if you want to make an elliptical selection, 100x200, and partly off screen? What if you want to make a 200x200 square, pulled out from the center instead of from a corner? I vote for closing as NOTABUG.
So how would you suggest I perform the task described?
IMO this sounds like an enhancement - displaying both the actual and effective selections sizes. Just limiting it in a different way, as this bug report suggests, isn't a solution.
Let's move it to the 2.4 milestone so that we get some more time to think about it. Changing that behaviour in the stable branch is probably not a good idea.
This is related to Bug 129189, and should be filed as 'major': a major loss of function.
There is no major loss of function. Please stop ranting, or do you think it's motivating to any volunteer who might be willing to implement this? I suggest simply displaying both sizes, as suggested in comment #5.
I never thought of enlarging the canvas as a way to accomplish this, or I would have been hitting this bug all the time too. To the original submitter: the new 2.3 rect select tool makes this sort of task a lot easier (at least with the fix for bug 326450 in place). Instead of enlarging the canvas, start the selection inside the canvas then resize it flush with the upper left edge (you can drag to a corner even though you can't easily start in a corner).
I don't see how it can be done without enlarging the canvas -- I either hit the ruler and get a guide or I'm a few pixels out. You people must have super motor control skills. Glad to hear about the fix :)
*** Bug 137050 has been marked as a duplicate of this bug. ***
If I start the selection inside (#9) or get a guide (#10), I can do any rectangle of any precision size. Maybe this could be included in the "tips of the day" to help this kind of 'problem' :). Or can be displayed the both sizes (the section size and the "canvas selection" size - I don't know how can we call that).
Displaying both sizes is what I suggested in comment #5.
The new rectangle select tool, which will be included with gimp 2.4, shows the bounds of the current rectangle in the tool options, so I am going to finally resolve this as FIXED.
And it's still wrong when doing so. See comment #3. Reopening.
In 2.3.11 the Select Tool shows both the size of the total selection box (Width and Height), and the coordinates shows the XY coordinates only as it relates to the actual image. So if you enlarge the window (as originally reported, not to be confused with increasing the canvas size) and start the select at -50,-50 and drag to 200,230 the Width=249 (close to 200+50), Height=279 (close to 230+50) and the coordinates of the selection show as 0,0 to 200,230 Essentially you get both pieces of information and can choose which one makes sense for your particular action. Also - setting snap-to-canvas-edge makes it quite easy to start a selection in a corner.
All right, we are now doing what the bug report asks for the crop tool, but not for the selection tools, and we have pretty solidly decided to stick with that, so I am going to resolve as NOTABUG.