Version: svn trunk OS: Linux The perspective grid is confusing users because it doesn't lock the tool, while the brush editor suggests that perspective will followed. Should we remove the perspective grid and only retain the perspective assistant? Reproducible: Didn't try Steps to Reproduce: x Actual Results: x Expected Results: x x
Is there any functionality that still requires the perspective grid that be done with the assistant (beside different look)?
Yes -- the way you can drag new grids out of an existing grid and lock perspective vanishing points.
It is confusing. Specially since the assistant perspective is very well hidden inside the Ruler assistant tool's options. A good setting (for the user logical point of view) would be to make the brush modifier act upon the perspective grid. (I added a pair of proposals to improve it in https://bugs.kde.org/show_bug.cgi?id=292684 ). Current perspective grid could be moved to the assistants tool. and the name "Ruler assistant editor tool" could be renamed to "Assistant editor tool" to communicate the idea that there are more than just one assistant available, with a "set square" triangle as the icon to avoid confusion with the line tool. Just my opinion, of course.
And then we can remove the perspective grid. WISHGROUP: Larger Usability Fixes
What exactly needs to be done here? The title suggests that the only thing that's left is clone tool working with perspective grid assistant, is that correct? (The comments don't mention it and mention a lot of stuff already done, like removing perspective grid or extending the perspective grid assistant).
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!