[Feature]: Grey Out Non-Working ALT-VBL Drawing Options
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The payload names no source files or tests. Start by finding where the drawing-method options (Fill, Line, X, Box) and the Cover, Hill and Pit VBL types are defined in the MapTool client. Decide how a selected topology should disable incompatible options, including the multi-select case the issue raises. Done means the options grey out correctly for single and combined selections, and the behaviour is confirmed by running the client.
Written by the indexing model from the issue text.
Description
Describe the Problem
When it comes to the many different ALT-VBL's we now have, it is too confusing trying to figure out which drawing type is needed for them to work correctly. Some BL's simply don't work if we select the wrong drawing method (Fill, Line, X or Box).
I think we can improve on this to help eliminate confusion.
The Solution you'd like
Grey out the drawing methods that simply won't work for the selected BL. Cover, Hill and Pit only work with fill, so grey out the other ones to remove that confusion that comes with over analysis.
Example:
The Wiki States only these 3 BL's having limitations:
Draw a hill VBL: this VBL will simulate the effect of an increased elevation level. Works only with the solid drawing tools.
Draw a pit VBL: this VBL will simulate the effect of an decreased elevation level. Works only with the solid drawing tools.
Draw cover VBL: this VBL will simulate the effect of shrubbery, fog, or other concealing effects. Works only with the solid drawing tools.
So how would that work when multi-selecting BL's to make a Franken-BL? Well, I guess if at least 1 of the above 3 are selected then the Franken-BL should have the non-fill options grayed out.
The idea here is to make it a lot less confusing for the user, especially new ones. This is one of the biggest struggles I have with the many different Topology options we now have - it hurts my brain.
Alternatives that you've considered.
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