You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be hard to see where a ladder will end up, and walking through it in analysis can take a long time.
Suggested feature during analysis mode: If the user taps out the first 4 stones of a ladder, show an almost completed ladder with partially transparent stones. The ladder would only auto complete to where it arrives within one (or two?) points of another stone.
Just that feature alone would be a huge help. But it could be taken a little further, eg: by tapping on the auto completed stones, they would turn to solid stones, as if the player had actually tapped them all out (tapping off of it would cancel / remove the autocompleted stones)
Thanks again for bringing to the community the best mobile go client out there!
The text was updated successfully, but these errors were encountered:
Tempted to attempt this, but at the same time, I feel it's better to train oneself to be able to read out ladders well, especially when half the time ladders are broken early anyway. For complicated situations analysis mode works well enough for me at least?
It can be hard to see where a ladder will end up, and walking through it in analysis can take a long time.
Suggested feature during analysis mode: If the user taps out the first 4 stones of a ladder, show an almost completed ladder with partially transparent stones. The ladder would only auto complete to where it arrives within one (or two?) points of another stone.
Just that feature alone would be a huge help. But it could be taken a little further, eg: by tapping on the auto completed stones, they would turn to solid stones, as if the player had actually tapped them all out (tapping off of it would cancel / remove the autocompleted stones)
Thanks again for bringing to the community the best mobile go client out there!
The text was updated successfully, but these errors were encountered: