https://bugs.kde.org/show_bug.cgi?id=440399
--- Comment #17 from [email protected] --- (In reply to Dmitry Kazakov from comment #7) > Yes, there is weird hack with transferring the focus from GUI elements to > the canvas. I'm not sure how we can solve that gracefully... > > The problem is, in general, we cannot distinguish, whether the user pressed > "Arrow Down" to change blendmode combo box (which is currently in focus) or > to pan the canvas. We use a weird hack for that: when the mouse hovers the > GUI elements, then GUI elements keep their input focus. When the mouse > starts hovering the canvas, Krita waits for a short period of time and then > transfers the focus to the canvas. The length of the delay depends on the > type of the control the focus belonged to. For normal controls the delay is > 400ms. For input boxes that allow actual typing the delay is 2000ms. > > If we remove the delay completely, then typing any values, like layer name > or opacity will be really cumbersome. You will have to ensure that the > stylus leaves the proximity on the GUI elements, not on the canvas. > > I don't know how to make this system better. If you have any solution, > please tell :) I'm sorry, I misclicked while meaning to reply to this post. :( Please see my suggestion in the above reply to tomtomtomreportingin. -- You are receiving this mail because: You are watching all bug changes.
