TextView with ScrollView: If TextView is set to read-only TAB and ENTER keys are eaten

This can be reproduced in the Wizard Scenario by setting helpTextView.CanFocus = false in WizardStep().

Not sure if this is a bug in TextView or ScrollView, or if there is a different way of enabling scrolling on TextView that works around this.

What I want is a read-only TextView that

a) Doesn’t take focus b) Can be scrolled with either mouse or keyboard

[tig]

Here’s the big idea:

A read-only TextView with a ScrollBarView is useful for displaying long text. When it is read only the user should be able to tab into and out of it. There is no world where it should eat tab presses when it is focused (and read-only).

Right now when ReadOnly == true the developer has to explicitly set AllowTabs = false for the control to work as expected.

The workaround is to set AllowTabs = false.

I assert this is a bug, and if ReadOnly == true the control should ACT as though AllowTabs == false. I do NOT think the fix is to automatically set AllowTabs when ReadOnly changes.

[tig]

CanFocus equal to false doesn’t allow to be focused. If you want use the scroll bar set the ReadOnly = false.

This is what I have done. helpTextView.ReadOnly = true. The problem is, when you tab into the helpTextView you can’t tab out.

But… I just discovered setting helpTextView.AllowTab = false addresses the issue.

In other words, the REAL bug here is when TextView.ReadOnly == true the view should IGNORE tabs (as though AllowTab = true).

Note that when AllowReturn is set to false, something else is goofy, but that’s another bug which I’ll file a separate issue on.