Might be best to not allow focus if the control is not editable. Set tabEnabled and/or focusEnabled=false.
On 9/19/13 2:45 AM, "Cosma Colanicchia" <[email protected]> wrote: >Hi, I have a little issue with the default TextInput component, could not >find it in already logged issues - at least I think so, there are a lot of >issues about text input components. > >This is the scenario: > >1) the component instance start with editable="false" >2) user moves focus to component using the keyboard >3) a particular key press activates editability of the field (through a >custom keyDown listener) >4) no cursor displayed, can't type in the field > >Notes: > - this is happening with the default (TLF-based) TextInput skin > - moving away focus and getting back to it (with keyboard or mouse, or >even with an ALT-TAB) cause the component to start behaving correctly > - if the instance has been previously editable, the behavior doesn't >reproduce > - if the focus is moved to the component through a mouse click the issue >is not triggered > > >As a workaround, I tried a callLater(textInput.setFocus) on my custom >keyDown listener, without success. Replacing the callLater with a >setTimeout also doesn't work (in both cases, it seems that its setFocus() >override of RichEditableText does nothing because the check on the compose >state of the text container manager. > >Any hint? >TIA
