-
-
Notifications
You must be signed in to change notification settings - Fork 431
Serial monitor scroll indicator/button #1838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @sterretjeToo. Thanks for your suggestion.
The suboptimal behavior of Serial Monitor under this condition is tracked at #1250. I think your suggestion of communicating the reason for this type of scrolling (which is different from autoscroll in that it doesn't scroll to the bottom of the output) is one reasonable option for mitigating that problem, so it would be best as a part of that discussion. Would you mind adding that part of your proposal in the thread of #1250?
Please do this:
|
Theme is Dark (Theia). I'm aware that it might disappear in the future ;) |
Yes. This theme improves the accessibility of Arduino IDE for people with vision impairments so Arduino does support it and there are no plans to remove it. |
Describe the request
I'm having great difficulty to see if I have selected scrolling in the serial monitor or not. One will usually be able to see it because of the scrolling / non-scrolling of the data but there is the condiction that, when the buffer is full, non-scrolling changes to scrolling without visual indication what was selected.
Please provide a means to see what is active (different icon, different colours, ...). There are three different scenarios that should be indicated
Implementation with different icons is prefered for those that are colour-blind.
Describe the current behavior
non-scrolling changes to scrolling without indication
Arduino IDE version
arduino-ide_nightly-20230128_Windows_64bit
Operating system
Windows
Operating system version
Win10 Home
Additional context
No response
Issue checklist
The text was updated successfully, but these errors were encountered: