Crop Tool

[Marpel]

PWP8 27Mar2019.

It appears the Crop Tool margin values up/down buttons don't work correctly. With arbitrary format, tried a couple times (after an initial crude movement of the crop rectangles) to move the top and side edges in by a couple clicks on the buttons. The values changed arbitrarily by a much larger amount and the crop rectangles jumped significantly to match the new values.

And, an unrelated question, why does the image change from 48 bit to 24 bit when Median Blur is used?

Marv

[jsachs]

The up/down controls for margins are standard Windows controls. If you hold the arrows down for too long, they start to count up automatically. One short click changes them by 1.

If you select variable radius median blur, the algorithm for fast median blur only works for 8-bits/channel images. The brute force median blur for large radius is complicated and quite slow. If you select 3x3 or 5x5, it can handle 16 bits/channel.

[Marpel]

Jonathan,

Thanks for the quick response.

OK, I understand the Median Blur thing now.

After your response on the Crop Tool, I was still a bit confused about what I had experienced, so I went and tried the tool again, just to clarify in my own mind what had happened. Here's what happened:

- Opened an image, 7360 X 4912 px.
- Did a coarse crop by moving the crop borders, to 3670 X 3786 (don't think those numbers are unique). The margin numbers were varied but the left was 1684 (no comma).
- Clicked the up arrow one time - left margin changed to 1,685 (now with a comma).
- Released the left mouse button after that single click but left the cursor over the button (don't know if leaving the un-clicked cursor over the button has anything to do with this).
- Almost immediately the number changed to 685 and the left crop line moved on the image to represent that 685.
- Did same thing a couple more times, with different numbers and the same general thing repeatedly occurred. As I recall, the same thing also occurred for the other margins when I tried it the first go round.

Don't know if the comma in the margin number has any bearing on this, but each time, the unanticipated new number was the old number, minus the comma and the number immediately to the left of the comma.

Marv

[jsachs]

The problem seems to have to do with the margin setting being greater than 999. It may take a little work to get this fixed. I am currently on vacation for the next few days so it will probably have to wait until I get back.