The example overridden isValid() method was just an example of allowing an empty string without the weird issues that Anton saw with other characters suddenly being accepted.
I haven't tested it within a row editor, just as a stand alone TextInput with a custom IntRangeValidator. A few months back, there were a couple of fairly long threads which resulted in changes to RowEditors. Greg tried a few variations, but I can't remember how it ended up. I think that it might still need a couple of tweaks to allow developers to target a specific row for editing. I think it should be possible to prevent the store() occurring if any values are invalid. Perhaps with a WindowStateListener on the RowEditor window to veto the close? I'll try to take a look tomorrow, but in the mean time, try searching the nabble archives. http://apache-pivot-developers.417237.n3.nabble.com/ http://apache-pivot-users.399431.n3.nabble.com/ Chris On 7 March 2011 03:08, lello <[email protected]> wrote: > Hi all, > I was having the same issue in the past days, and I was trying to find a > solution, but without success. > I'll try what Chris suggests. > > Another issue with the validation is the following: if you have no strict > validation (setStrictvalidation(false)) you can type and invalid character, > but if you select a second row with the > mouse the store() method is called, which of course result in an exception. > I don't know if this is a bug or it is intended to be like this. I'd prefer > the table to be not responsive when any of its field is not valid. > > > > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/TextInput-and-Validator-issues-tp2641141p2643010.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com. >
