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

[PrudhviPathipati]

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.

 

 

[RyukShini]

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?
 

[PrudhviPathipati]

; 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.

[PrudhviPathipati]

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

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

[PrudhviPathipati]

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.

[water]

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.

[RyukShini]

#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 June 20, 2016 by RyukShini

[ViciousXUSMC]

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.

expandcollapse popup

#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.

[RyukShini]

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.

expandcollapse popup

#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!
 

[spudw2k]

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 June 20, 2016 by spudw2k

[mLipok]

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

mLipok

 

[spudw2k]

@mLipok Thanks for the heads up.  fixed