DCTTextFieldValidator takes an array of UITextFields and validates them before allowing an action to take place.
It switches the return key depending on whether or not the text fields are valid, if one or more text fields are invalid, it will make the next one in the array the first responder upon tapping the return key. Once all fields are valid, the keyboard return key will become (for all text fields in the array) that which is assigned to the last text field in the array.
The main thinking is to make sure all of the fields are filled out, and not blank. Though I am considering a post-validation, which would validate each one after the return key is hit, such as checking emails are correct and such. I’ve filed this as a bug on GitHub and would be grateful for any input on this.
This project uses ARC.
There is some documentation for DCTTextFieldValidator generated with appledoc.
There are two branches to this repository, master and demo.
The master branch contains the code and should be used if you want to add these extensions as a git submodule in other projects. It will only contain the class files themselves without the Xcode project or example classes. This is preferable as it will keep your directories clean of any code which is unnecessary to your working project.
To add this project as a submodule you should run the following from inside your project’s git repository:
git submodule add git://github.com/danielctull/DCTTextFieldValidator.gitTo keep up to date with the latest changes `cd` into the directory that contains this submodule and pull the newest changes as usual:
git pull originThis contains an Xcode project that demonstrates the code and is the branch to use to see how to use the code. The demo branch contains a submodule reference to the master branch to bring in the library classes.
To clone the demo branch, while also pulling in any necessary submodules run the following command:
git clone -b demo --recursive git://github.com/danielctull/DCTTextFieldValidator.gitWhen changing to the demo branch you will need to run through the following set of commands:
git checkout demo
bc. git submodule init
bc. git submodule updateAfter these you will see the example project and the library code will be in a sub-directory.
Sometimes, there may be artefacts left over when switching from demo to master. These are files that are ignored by git and are easily cleaned up by running
git clean -dxfCopyright © 2011 Daniel Tull. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.