[
https://issues.apache.org/jira/browse/PIVOT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903422#action_12903422
]
Greg Brown commented on PIVOT-616:
----------------------------------
I hadn't planned on doing that, but it would be very easy to write one. The
listener could potentially wrap a validator.
Maybe it would make sense to retain the "strictValidation" property, but at the
component level rather than in the skin. I tried this a while back and reverted
it - I don't remember why. Maybe I will take another stab at it.
> TextInput API improvements
> --------------------------
>
> Key: PIVOT-616
> URL: https://issues.apache.org/jira/browse/PIVOT-616
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Greg Brown
> Fix For: 2.0
>
>
> Make the following updates to the TextInput API, to improve performance and
> to align API with that of new TextArea:
> - Add a getCharacters() method that returns a CharSequence representing the
> text input's content.
> - Rename insert()/delete() to insertText()/removeText(), and change insert
> behavior such that the caller is responsible for performing the delete rather
> than the insertion method.
> - Rename TextInputTextListener to TextInputContentListener.
> - Change charactersInserted() to textInserted() and charactersRemoved() to
> textRemoved(); replace characters argument in textRemoved() with a character
> count to optimize performance (eliminate unnecessary string copy).
> - Make text insert/remove events vetoable, replacing "strictValidation" style
> in TerraTextInputSkin.
> - Remove getTextLength(); superseded by getCharacters().length().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
