Remove the automatic scrolling to the top in Layers tab of Route and Mark Manager
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by locating the Route and Mark Manager implementation and reproduce the issue in its Layers tab by scrolling down and toggling a layer's visibility. Done means the list no longer jumps to the top and the same layer remains selected so its visibility can be toggled again.
Written by the indexing model from the issue text.
Description
In the Route and Mark Manager, after selecting the Layers tab, you can toggle the visibility of a layer. When you scroll down and then toggle the visibility of a layer to "on", the scroll bar returns to the top. When you then want to toggle the same layer off again, you first have to scroll down and find it back. This is not intuitive and contrary how you expect this to work.
I propose to delete the scrolling to the top after toggling visibility of a layer, and keep the same layer selected. So you can quickly toggle a layer on and off again.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 627
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 9
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 OpenCPN/OpenCPN
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenCPN/OpenCPN#5413 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Include git commit hash in version information for builds in local workspaceMay be free again A pull request for this issue was closed without being merged. Openenhancement
Difficulty 1/5 Under an hour Newbie friendliness 70/100
OpenCPN/OpenCPN#4753 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
RFE: Tide dialog for route point ETA.Possibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenCPN/OpenCPN#4422 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
contrib/ivorysql_ora/src/builtin_packages/utl_file/utl_file.c:517 - FCOPY destroys a file when source and destination are the samePossibly taken @Metastarx claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
ly05010419/MacNativeGames#1848 ·
Maintainers usually reply within 1 day
-
libc++ test-suite
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
llvm/llvm-project#239851 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day