I luv it thanks..
I have a couple observations which are really trivial and I don't really know if they are worth any attention because could be just semantics, but they are worth mentioning..
First, regarding the selection box, which are Top/Left and Bottom/Right outlines. you can move and position the x & y co-ordinates which define the Left outline and Top outline, so that the top/left selection outlines are positioned over a window border using the arrow keys or L/l R/r keys.
then you can move and position the h & w co-ordinates (I assume Height and Width) which define the bottom outline and right outline, so that the bottom/right selection outlines are positioned over a window border using the arrow keys or X/x and Y/y keys.
Maybe there is some technical reason why we can't move the x and y co-ordinates with the arrow keys and X/x and Y/y keys. Then move the W and H co-ordinates with W/w and H/h keys.. Sounds good right??
Secondly, this is more difficult to explain.. When you position the selection box exactly over the desired window border lets say over the outermost one pixel width of the widow border, the top & left selection components capture the one pixel beneath the selection bars. Whereas the right & bottom (W & H) selection bars do not capture the one pixel of the window border directly beneath them, ie the saved window shot is missing the one pixel off the bottom and right sides. Conversely you could say that the top and left portion of the saved window shot have gained the extra one pixel of the window border.
Honestly I don't know which is right, but I think the x/y and w/h selection co-ordinates should capture the same. That is either the pixel inside the border or the pixel underneath, for all sides of the selection box. I'm thinking if you draw a box around a window you should capture every pixel inside that selection., seems logical..?
sorry if that's clear as mud...