You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The selection can be modified using the arrow keys without using the move tool, breaking some of the assumptions of canvaspainter.
Actual Results
When a selection is made, moved with the arrow keys and then the canvas is painted on with a drawing tool, all without selecting the move tool, then this assert will be triggered, and crash on debug builds.
If the assert is ignored, as it would be in a release build, then the selection does not get applied before drawing and the drawing tool will behave as if the selection has not been transformed. This will result in some visual anomalies as the brush data conflicts with the selection data. After each stroke is finished, the program behaves as if the stroke had been drawn before the selection was transformed, and the selection remains active with a transformation.
Expected Results
It is expected that the assert does not fail obviously. Perhaps the easiest and best solution would be for the arrow key shortcuts to only transform selections while the move tool is active. It would also make sense to be able to move the selection bounds (without the content) with the arrow keys when the select tool is active.
Steps to reproduce
Create a selection.
Switch to the pen tool.
Use the arrow keys to move the selection.
Attempt to draw through the selection with the pen tool.
This issue was previously noted in the PR in which it was introduced (#1807 (comment)), though after it had already been merged. I have created this separate issue for tracking purposes.
The text was updated successfully, but these errors were encountered:
Issue Summary
The selection can be modified using the arrow keys without using the move tool, breaking some of the assumptions of canvaspainter.
Actual Results
When a selection is made, moved with the arrow keys and then the canvas is painted on with a drawing tool, all without selecting the move tool, then this assert will be triggered, and crash on debug builds.
If the assert is ignored, as it would be in a release build, then the selection does not get applied before drawing and the drawing tool will behave as if the selection has not been transformed. This will result in some visual anomalies as the brush data conflicts with the selection data. After each stroke is finished, the program behaves as if the stroke had been drawn before the selection was transformed, and the selection remains active with a transformation.
Expected Results
It is expected that the assert does not fail obviously. Perhaps the easiest and best solution would be for the arrow key shortcuts to only transform selections while the move tool is active. It would also make sense to be able to move the selection bounds (without the content) with the arrow keys when the select tool is active.
Steps to reproduce
System Information
Developer Notes
This issue was previously noted in the PR in which it was introduced (#1807 (comment)), though after it had already been merged. I have created this separate issue for tracking purposes.
The text was updated successfully, but these errors were encountered: