Version: recent SVN, says 0.90.0 (using KDE Devel) Installed from: Compiled sources Compiler: gcc 4.1 OS: Linux snap-to-closest point doesn't work as I'd like it to. If I draw a line and then a circle intersecting that line, any click falling near an intersection point should be automatically snapped to that intersection. Even if I didn't formally define a point at that intersection. I know that it's an annoying feature request because it seems to mean that Kig has to process through all existing shapes everytime a click is made, which would be very costly in complex figures. Fortunately it should be possible to discard most shapes quickly, for instance if a click falls far away from a circle then one can safely ignore that circle. If that kind of technique turns out to not be enough, some form of BSP trees (or whatever is hip at the moment) should do the job. Just one thought I just had while writing this: could QGV help here? It allows to handle scenes with many shapes, handles clicks on these shapes, and scales very well to large numbers of shapes thanks iirc to a BSP-like technique.
I'm not really sure snapping should snap by intersection points as well. The idea that started some time ago was to have MMB-click to construct a point as intersection of the two objects under the mouse. Though, currently only works for lines only.
It's your app, so you get to decide :) All I can say is that for me the most useful behavior (hence the one I'd like to be default) is snapping. Also: please allow the use of a keyboard modifier (like Ctrl) for machines without a 3-button mouse (touchpads, macs). 3rd button emulation through simultaneous clicking of 2 buttons is not very convenient. --Benoit
> It's your app, so you get to decide :) That's what wish and bug report are for ;) > Also: please allow the use of a keyboard modifier (like Ctrl) for machines > without a 3-button mouse (touchpads, macs). 3rd button emulation through > simultaneous clicking of 2 buttons is not very convenient. That is indeed an sensible request.
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? 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!