Make it clearer when something is a preview
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 869
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
## Use case
for all these things:
- drawing free shape or polygon
- 2-steps curves
- rotating
- ...?
it's not clear that the preview is indeed just a preview
## Suggested solution
- 8-handled dashed overlay for:
- [ ] skew
- [ ] rotate
- [ ] design and implement dashed overlays for paths, and use it for:
- [ ] 2-steps curves
- [ ] polygons
- [ ] free shapes
- [ ] preview the expected tool thickness when pressing ctrl
### Possible drawbacks
im not a big fan of dashed overlays for paths
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how previews are handled for free shapes, polygons, two-step curves, skew, and rotation, then define completion against the listed overlay and thickness-preview ideas while resolving the stated concern about dashed path overlays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100