Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How Tab and Shift+Tab keys should be performed on TextView?

See original GitHub issue

In my opinion Tab should insert the char 9 and the Shift+Tab should retreat the char 9 to the previous column, because on a multiline editor is normal to press the tab key to insert spaces and and Shift+Tab to remove spaces. So, if it goes to the next view, forces us to go to the TextView again causing stressing.
Another solution is replacing the tabs to spaces, but if the original text has tabs it should be maintained. Perhaps an option to convert to spaces or vice-versa.
For navigation Ctrl+Tab should go to the next view and Ctrl+Shift+Tab should go to the previous view.
Please, give your opinions to makes this definitively clear. Thanks in advance.

Issue Analytics

State:
Created 2 years ago
Comments:8

Top GitHub Comments

2reactions

tigcommented, Apr 16, 2021

I think this is a good plan.

2reactions

tznindcommented, Apr 15, 2021

In WinForms there is a boolean property for this AcceptsTab and also AcceptsReturn (both default to false). Not sure if that helps just thought I’d add another perspective.

https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.textboxbase.acceptstab?view=net-5.0

https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.textbox.acceptsreturn?view=net-5.0