PrudhviPathipati

INPUT - IP VALIDATION - SHOULD ACCEPT NUMBERS AND DOT ONLY.

12 posts in this topic

Hi to All,

Sorry to disturb.

I am new to AutoIT scripts, My question is how to restrict special characters except dot for IP validation. 

Thanks in advance.

 

 

Share this post


Link to post
Share on other sites
8 minutes ago, PrudhviPathipati said:

Hi to All,

Sorry to disturb.

I am new to AutoIT scripts, My question is how to restrict special characters except dot for IP validation. 

Thanks in advance.

 

 

Do you have some example code?
Something to start from.
Could you be a bit more specific?
Are you reading IPs from a file or from a web page?
 

Share this post


Link to post
Share on other sites

; IP LABEL
$LblIP = GUICtrlCreateLabel("IP* :", 65, 110, 170, 20)

; IP Input box
$TxtSIP = GUICtrlCreateInput("", 160, 110, 140, 21)
GUICtrlSetLimit($TxtSIP, 15,1)

$BtnOK = GUICtrlCreateButton("CONFIRM", 150, 280, 75, 45)

FileWriteLine("C:\info.txt",$TxtSIP)

On button click event ,if the condition is satisfied then IP value saving in text file.

If not specific please let us know.

Share this post


Link to post
Share on other sites

CHECKING IS ANY SPACE AVAILABLE - $SpaceValip = StringRegExp($GetAIP,"\s")

SET MIN VALUE IS 7 - $StrLen = StringLen($GetAIP)

Share this post


Link to post
Share on other sites

Local $iPosition = StringInStr($ TxtSIP , ".")

If iPosition = 0 then 

Msgbox(16,"Alert Message","IP Format is wrong")

Else

Msgbox(16,"Alert Message","IP Format is Correct")

Endif

What i have faced here, if the customer is input like 10.323.@3.131, then i am unable restrict.

Share this post


Link to post
Share on other sites

IIRC this subject has been discussed a few times on the Forum. Search the Forum for "IP Input Validation" or something similar and I'm sure you will get some hits.


My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2017-04-18 - Version 1.4.8.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX (NEW 2017-02-27 - Version 1.3.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2015-04-01 - Version 0.4.0.0) - Download - General Help & Support - Example Scripts
Excel - Example Scripts - Wiki
Word - Wiki
PowerPoint (2015-06-06 - Version 0.0.5.0) - Download - General Help & Support

Tutorials:
ADO - Wiki

 

Share this post


Link to post
Share on other sites

#7 ·  Posted (edited)

#include <MsgBoxConstants.au3>

Local $sAnswer = InputBox("IP", "InputIP")
if StringInStr($sAnswer, "@") Then
MsgBox(4096, "test", "Now Allowed")
Else
    MsgBox(4096, "Success", "Accepted")
EndIf
Exit

Tell me if this is what you were looking for, at least it reports an error on my end if you input @
as @water said, please search the forum for "IP input validation" before asking this.
I actually forgot to search before writing this xD

Edited by RyukShini

Share this post


Link to post
Share on other sites

Depends on how you want to do it.

On GUI's I prefer to restrict the users from even typing data that I do not want them to enter rather than validate it after the fact.

A basic number & period only validation would look like this ($input2). You can further enhance it so that it must contain 3 periods, etc.

#include <EditConstants.au3>
#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>

$Form1 = GUICreate("Test GUI", 618, 276, 192, 124)
$Label1 = GUICtrlCreateLabel("Test GUI", 168, 24, 47, 17)
$Button1 = GUICtrlCreateButton("Toggle Validation", 290, 24, 110, 40)
$Input1 = GUICtrlCreateInput("Max 10 Characters", 40, 72, 553, 21)
$Input2 = GUICtrlCreateInput("Numb3rs & Period 0nly", 40, 97, 553, 21)
$Edit1 = GUICtrlCreateEdit("Max 10 Chars Numbers Only + Auto Line Break", 40, 120, 553, 105)
GUISetState(@SW_SHOW)

$iToggle = 1

GUIRegisterMsg($WM_COMMAND, '_WM_COMMAND')

While 1
    Sleep(10)
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            Exit
        Case $Button1
            $iToggle = $iToggle + 1
    EndSwitch
WEnd

Func _GUIRegExValidate($sInputLabel, $sRegExCapture, $sRegExReplace)
    $Step1Read = GUICtrlRead($sInputLabel)
    $Step2Validate = StringRegExpReplace($Step1Read, $sRegExCapture, $sRegExReplace)
    If @Extended = 0 Then Return
    GUICtrlSetData($sInputLabel, $Step2Validate)
EndFunc

Func _WM_COMMAND($hWnd, $Msg, $wParam, $lParam)
If Mod($iToggle, 2) = 0 Then
;Example 1 Limit to 10 Characters
 _GUIRegExValidate($Input1, "(.{10})(.)", "$1")
;Example 2 Can only type numbers and period
 _GUIRegExValidate($Input2, "[^\d.]", "")
;Example 3 Combind More Than One On Same Input limit to 10 characters, limit to numbers only, line break @ 10 characters to new line
 _GUIRegExValidate($Edit1, "(.{10})(.)", "$1" & @CRLF)
 _GUIRegExValidate($Edit1, "[^\d\r\n]", "")
 EndIf
EndFunc

This was my crude invention for input validation, works for me but I am sure there are even better ways to do it.

Share this post


Link to post
Share on other sites
22 minutes ago, ViciousXUSMC said:

Depends on how you want to do it.

On GUI's I prefer to restrict the users from even typing data that I do not want them to enter rather than validate it after the fact.

A basic number & period only validation would look like this ($input2). You can further enhance it so that it must contain 3 periods, etc.

#include <EditConstants.au3>
#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>

$Form1 = GUICreate("Test GUI", 618, 276, 192, 124)
$Label1 = GUICtrlCreateLabel("Test GUI", 168, 24, 47, 17)
$Button1 = GUICtrlCreateButton("Toggle Validation", 290, 24, 110, 40)
$Input1 = GUICtrlCreateInput("Max 10 Characters", 40, 72, 553, 21)
$Input2 = GUICtrlCreateInput("Numb3rs & Period 0nly", 40, 97, 553, 21)
$Edit1 = GUICtrlCreateEdit("Max 10 Chars Numbers Only + Auto Line Break", 40, 120, 553, 105)
GUISetState(@SW_SHOW)

$iToggle = 1

GUIRegisterMsg($WM_COMMAND, '_WM_COMMAND')

While 1
    Sleep(10)
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            Exit
        Case $Button1
            $iToggle = $iToggle + 1
    EndSwitch
WEnd

Func _GUIRegExValidate($sInputLabel, $sRegExCapture, $sRegExReplace)
    $Step1Read = GUICtrlRead($sInputLabel)
    $Step2Validate = StringRegExpReplace($Step1Read, $sRegExCapture, $sRegExReplace)
    If @Extended = 0 Then Return
    GUICtrlSetData($sInputLabel, $Step2Validate)
EndFunc

Func _WM_COMMAND($hWnd, $Msg, $wParam, $lParam)
If Mod($iToggle, 2) = 0 Then
;Example 1 Limit to 10 Characters
 _GUIRegExValidate($Input1, "(.{10})(.)", "$1")
;Example 2 Can only type numbers and period
 _GUIRegExValidate($Input2, "[^\d.]", "")
;Example 3 Combind More Than One On Same Input limit to 10 characters, limit to numbers only, line break @ 10 characters to new line
 _GUIRegExValidate($Edit1, "(.{10})(.)", "$1" & @CRLF)
 _GUIRegExValidate($Edit1, "[^\d\r\n]", "")
 EndIf
EndFunc

This was my crude invention for input validation, works for me but I am sure there are even better ways to do it.

This really helped me understand things in another way, thanks a lot!
 

Share this post


Link to post
Share on other sites

#10 ·  Posted (edited)

I suppose the value of knowing how to do this kind of input validation could be and is useful for many things...but I just wanted to offer another idea specific to IP address.  Have you seen the _GUICtrlIpAddress_ functions/UDF?  It can be used to build a decent IP address input field which enforces "valid" IP addresses.  I "finished" a subnet calculator recently which uses the GUIIP (SysIPAddress32) controls if you want a demo.

edit: typo and clarification

Edited by spudw2k

Share this post


Link to post
Share on other sites

@spudw2k Whats happend to your signature ? I ask about spoiler - can you re-edit your signature ?
btw. recently I had the same problem :)

mLipok

 


Signature beginning:   Wondering who uses AutoIT and what it can be used for ?
* GHAPI UDF - modest begining - comunication with GitHub REST API *
ADO.au3 UDF     POP3.au3 UDF     XML.au3 UDF    How to use IE.au3  UDF with  AutoIt v3.3.14.x  for other useful stuff click the following button

Spoiler

Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind. 

My contribution (my own projects): * Debenu Quick PDF Library - UDF * Debenu PDF Viewer SDK - UDF * Acrobat Reader - ActiveX Viewer * UDF for PDFCreator v1.x.x * XZip - UDF * AppCompatFlags UDF * CrowdinAPI UDF * _WinMergeCompare2Files() * _JavaExceptionAdd() * _IsBeta() * Writing DPI Awareness App - workaround * _AutoIt_RequiredVersion() * Chilkatsoft.au3 UDF * TeamViewer.au3 UDF * JavaManagement UDF * VIES over SOAP * WinSCP UDF * GHAPI UDF - modest begining - comunication with GitHub REST API *

My contribution to others projects or UDF based on  others projects: * _sql.au3 UDF  * POP3.au3 UDF *  RTF Printer - UDF * XML.au3 - BETA * ADO.au3 UDF SMTP Mailer UDF *

Useful links: * Forum Rules * Forum etiquette *  Forum Information and FAQs * How to post code on the forum * AutoIt Online Documentation * AutoIt Online Beta Documentation * SciTE4AutoIt3 getting started * Convert text blocks to AutoIt code * Games made in Autoit * Programming related sites * Polish AutoIt Tutorial * DllCall Code Generator * 

Wiki: Expand your knowledge - AutoIt Wiki * Collection of User Defined Functions * How to use HelpFile * Best coding practices * 

IE Related:  * How to use IE.au3  UDF with  AutoIt v3.3.14.x * Why isn't Autoit able to click a Javascript Dialog? * Clicking javascript button with no ID * IE document >> save as MHT file * IETab Switcher (by LarsJ ) * HTML Entities * _IEquerySelectorAll() (by uncommon) * 

I encourage you to read: * Global Vars * Best Coding Practices * Please explain code used in Help file for several File functions * OOP-like approach in AutoIt * UDF-Spec Questions *  EXAMPLE: How To Catch ConsoleWrite() output to a file or to CMD *

"Homo sum; humani nil a me alienum puto" - Publius Terentius Afer
"Program are meant to be read by humans and only incidentally for computers and execute" - Donald Knuth, "The Art of Computer Programming"
:naughty:  :ranting:, be  :) and       \\//_.

Anticipating Errors :  "Any program that accepts data from a user must include code to validate that data before sending it to the data store. You cannot rely on the data store, ...., or even your programming language to notify you of problems. You must check every byte entered by your users, making sure that data is the correct type for its field and that required fields are not empty."

Signature last update: 2017-06-04

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now