terrible to paste pictures.

[Lin3er]

Dear author, in the process of comparing and using it, I found that chreetree was not very friendly in the display picture, which is as follows:

1. The paste picture is very large in the editor, and you need to scroll through the scroll bar to see all of them. This kind of logical operation is very cumbersome. It is recommended that the picture can be adjusted in proportion. If the pasted picture exceeds the width and length of the current editor, it will be reduced to 70% and 80% of the editor.

2. There is distortion after resizing the picture, and the specific treatment needs to be solved according to the previous implementation method.

Thank you very much for your efforts in cherrytree.

[ArenT1981]

I think the current handling/treatment of pasted images is in general absolutely fine. You suggest:

If the pasted picture exceeds the width and length of the current editor, it will be reduced to 70% and 80% of the editor.

However this makes no sense, due to the fact that width/length of the editor is entirely dependent on the current size of the application window, to whatever the user has resized it to using their window manager. I think what you're asking is that the image display could have a feature where it automatically dynamically resizes (in memory, not the actual stored image data) the displayed image such that it is scaled to some percentage of the editor width, say 80%, as you suggest. If so, I suppose that could be added as a preference toggle, or possibly right-click context option.

Some (most?) of us actually want the image to always be 100% scaled, even if we paste in a huge 4k screenshot (for example), precisely because that way all of the detail in the image is clear. Using a horizontal scrollbar in such a scenario to move across the image works just fine.

Personally I think the current functionality, where you can right-click and destructively resize within Cherrytree, if you wish, is near perfect behaviour. Some people might prefer that it always retains the original image data, and allows you to do a "non-destructive" resize, but again, this should probably be a preference toggle, as if you've decided to explicitly scale down the image, storing the full size image would be considered a waste of storage in the Cherrytree database in that scenario. After all, if you still/also wanted to retain a full-size copy, you could also attach that within the node, but as a file attachment rather than as in-line displayed image.