Repository navigation
User interface #2058
Replies: 7 comments 6 replies
|
@kindelksoft Thanks for bringing this up! My apologies on the delay in response. I think we can create feature requests for discrete parts of your suggestion. Can we start by identifying the most important single change that would help this problem? |
|
Thank you for your work and for your response to the problems.
|
|
Samsung Galaxy A26 5G. SM-A266B/DS. Android - 16. COTGUI.mp4It would be nice if the bottom panel disappeared when the keyboard was opened. UI.mp4 |
|
Xiaomi Redmi 10 Note Pro Android - 13. Same problem. |
|
And again UI. Above the keyboard, such a field periodically appears. COTG-26.41 Screen_Recording_20261007_100218_Code.on.the.Go.mp4 |
|
Does this only occur with the soft keyboard. |
|
Hi @kindelksoft, thanks for confirming that detail — noted that the stray field above the keyboard only appears when using the soft keyboard. Quick update on the swipe issue: the inaccurate output-panel swipe detection reported in #2078 has been addressed. PR #2183, "Ignore output-panel drags that start above its visible edge," was merged on October 30, 2026. The change ignores drags that begin above the panel's visible edge. Once a version containing this change is available, please check whether the accidental panel openings still occur. The request to hide the bottom panel while the keyboard is open is still tracked separately as feature request #2076, which remains open. Thanks again for the detailed reports and videos — they helped clarify both issues. |
Uh oh!
There was an error while loading. Please reload this page.
First, I want to thank the developers for all the
hard work they’ve put in. I want to apologize for the criticism that follows.
You’ve created a great multi-tool.
You pick it up, open the tool you need, and look forward to
enjoying your work. The phone screen is small, and
you accidentally tap the wrong spot, bringing up the wrong
tool. You close it, but it keeps opening
again and again... And coding turns into a
quest game you no longer want to play.
Opening something by dragging is great, but if
it doesn’t work properly, it turns into
a nightmare and a waste of time. The main task with COTG
is writing code. Nothing should get in the way of that,
least of all a cautious movement. Everything other than the editor
are auxiliary tools that you spend less
time using. If that requires clicking somewhere
that isn’t in a convenient spot, that’s better than a mistaken click
in a convenient spot.
Compare this:
COTG
https://github.com/user-attachments/assets/4f7b1884-d663-4575-b421-fc543572c132
ACS
https://github.com/user-attachments/assets/0ef82016-d592-4d85-a0a3-35e1cb0bbcb4
All reactions