[Bug]: Scale change with hex grids not keeping hexes properly.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 64/100
Research direction
Reproduce on a hex-grid map via Map Menu → Adjust Grid: mouse-wheel on Grid Size should keep the second hex dimension in proportion, while typing or using the spinner arrows should not. Locate the Adjust Grid UI handlers for Grid Size versus wheel input and the hex-grid size fields they update. Done when both input paths scale the second size with the first so hexes stay symmetrical, matching the wheel behavior.
Written by the indexing model from the issue text.
Description
Describe the Bug
When using "Adjust Grid" on a map with hexes, if you use a mouse wheel to change the grid size, things behave as expected. However if you use the "Grid Size" box to put in a value to get more precise control, the "Second Size" value does not change, leading to progressively more distorted hexes.
To Reproduce
- Create a map and set hexes as the grid type. Either type of hex will work.
- Open the Map Menu and Select "Adjust Grid".
- Change the Grid Size either by putting in a different value (it will be most visible if you make a large reduction, such as 100 to 80) either manually, or with the toggle arrows (this will not occur if you use a mousewheel)
- The hexes will be distorted, as the 2nd Value will not change.
Expected Behaviour
What should occur (and does with use of the mouse wheel) is the 2nd value should change in proportion to primary value, leaving more or less symmetrical hexes.
Screenshots
MapTool Info
Windows: 1.18.6
Desktop
No response
Additional Context
No response
- Dominant language
- Java
- Stars
- 927
- Forks
- 286
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 94
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from RPTools/maptool
-
[Bug]: An initiative list with no current entry logs an error on every changePossibly taken @dwizard0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
[Maintenance]: Migrate gradle dependency submission to modern alternativePossibly taken @VelpulaGangavardhan claimed this 18 days ago. Opencode-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
RPTools/maptool#6156 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
code-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
Similar issues
-
Cleanup: restore the interrupt flag in AiFailureAnalyzerPossibly taken @Rishankgupta08 claimed this today. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seleniumboot/selenium-boot#258 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
johanhaleby/occurrent#1505 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FasterXML/jackson-databind#6443 ·
Maintainers usually reply within 1 day
-
Docs: 2 broken linksOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day