Pixels are not alligned to grid for a 32x20 grid
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 49/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- zig
- Domain
- design
Research direction
Start by locating the grid rendering and pixel-placement entry points in the Zig editor; the issue does not name files or tests. Reproduce the mismatch with a 32x20 grid and compare where grid lines fall against placed pixels. Done means pixels align with the grid at that size; the report gives no specific test or expected implementation.
Written by the indexing model from the issue text.
Description
Pixels are not in "sync" with grid.
I'd expect pixels to fall in place within a grid, since that makes it easier to allign the sprites.
When using a grid of 32x20 the grid is not alligned with where the pixels are placed. It looks to me like the grid is 2.5 pixels wide instead of a whole number.
Maybe this should have been opened on the Pixi repository but I found it odd that this pixel editor didn't come with the Pixel editing functionality. I had to track down this other repository (plugin) and build it myself (the plugin store does not find any compatible plugins on linux_x64).
- Dominant language
- Zig
- Stars
- 1.5k
- Forks
- 40
- Avg merge
- 5h 35m
- Merged PRs (30d)
- 151
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from fizzyedit/fizzy
-
replay: bench-replay no longer compiles, and nothing in CI builds itPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fizzyedit/fizzy#306 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
Similar issues
-
css docs v6
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area: editor design good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
aaronified/fluenough#466 ·
Maintainers usually reply within 1 day
-
good first issue help wanted track:ui
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Sara-Managed-Projects/space-radar#703 ·
Maintainers usually reply within 1 day
-
Needs-Triage Product-FancyZones
Difficulty 2/5 Half a day Newbie friendliness 65/100
microsoft/PowerToys#51172 · 1 comment ·
Maintainers usually reply within 1 day