Selecting and deselecting shapes is either somewhat broken or just unintuitive. (check steps to reproduce) Reproducible: Always Steps to Reproduce: 1. While editing text, 2. Click on an image, the "Picture editing tool" in the docker opens, but you cannot tell that the image is selected just by looking at the image (there are no borders with handles for resizing) 3. Select "Text editing" or "Basic shape manipulation" or pressing escape the border with handles appear around the image and in all 3 cases "Basic shape manipulation" opens 4. Double click on some text to go back to text editing 5. Double click on an image shows "open file" dialog (?!) Expected Results: Discovering these behaviours might be difficult and unintuitive. There are many ways to solve this issue, here is my suggestion: 1. when user clicks on an image (or any shape in general), "Basic shape manipulation" should open up, and in the toolbar, an edit button appears (+in the context menu). 2. at this point you can resize the shape etc. and go back to text editing clicking once on another part of the document 3. or you can select edit in the toolbar or double click on the image to go to open "Picture editing tool". 4. now there should be some kind of decoration/border on the image to indicate that it is in editing mode. and in the toolbar the edit button changes to "done" 5. now you can go back to step 2 by double clicking outside the image or pressing "done" or escape or clicking on "basic shape manipulation" in the docker
Thanks As far as the weirdness of the current interaction I fully agree, and I've been working on various alternatives for the last half year (on and off). We have several things to take into consideration, and I'll think about your suggestion when continuing the work.
*** Bug 321168 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!