Sign in to follow this  
Followers 0
NeverDUN

Help with GUI script needed.

2 posts in this topic

#1 ·  Posted (edited)

Ok so thus far the script does what it's suppose to do.. to a point. 

There are two complications and they are as follows:

  • There is suppose to be ONE GUI that opens up.

When i run the script it opens, but when i close it another identical one opens behind it.

  • When i click save on the first GUI it saves like it's supposed too.

BUT when i close it and reopen it, it's suppose to open with the info that was saved.

I'm no pro coder, maybe it's something very small i'm not getting.

Some help would be highly appreciated.

Yea.. i have it saving alot :3

#include <ButtonConstants.au3>
#include <EditConstants.au3>
#include <MsgBoxConstants.au3>
#include <GUIConstantsEx.au3>
#include <GuiStatusBar.au3>
#include <ProgressConstants.au3>
#include <WindowsConstants.au3>


Do
    $pass = InputBox("Enter Password", "Please enter the password", "", "*", 150, 120)
    If $pass <> "Password" Then
    EndIf
    If (@error == 1) Then Exit ;
Until $pass == "123"
MsgBox(0, "Success", "Correct password" & @CRLF & "")

Global $sConfigPath = @ScriptDir & "\Settings.ini"

ProgressOn("Title", "Loading program", "Loading...")

For $i = 0 To 100
    ProgressSet($i)
    Sleep(5)
Next

ProgressSet(50, "Half Way.")
Sleep(250)

ProgressSet(100, "Done!")
Sleep(750)
ProgressOff()

#Region ### START Koda GUI section ### Form=
$Form1 = GUICreate("Title", 610, 477, 206, 143)
$Input1 = GUICtrlCreateInput("Date", 480, 16, 113, 21)
$Input2 = GUICtrlCreateInput("Title", 16, 56, 577, 21)
$Edit1 = GUICtrlCreateEdit("", 16, 80, 577, 329)
$Button1 = GUICtrlCreateButton("Save", 520, 424, 75, 25, $BS_DEFPUSHBUTTON)
$idProgressbar1 = GUICtrlCreateProgress(16, 424, 454, 17)
$StatusBar1 = _GUICtrlStatusBar_Create($Form1)
GUICtrlSetColor(-1, 32250)
GUISetState(@SW_SHOW)

Local $iWait = 20; wait 20ms for next progressstep
Local $iSavPos = 0; progressbar-saveposition

Local $idMsg, $idM
; Loop until the user exits.
Do
    $idMsg = GUIGetMsg()
    If $idMsg = $Button1 Then
        GUICtrlSetData($Button1, "Stop")
        For $i = $iSavPos To 100
            If GUICtrlRead($idProgressbar1) = 50 Then MsgBox($MB_SYSTEMMODAL, "Info", "half is done...", 1)
            $idM = GUIGetMsg()

            If $idM = -3 Then ExitLoop

            If $idM = $Button1 Then
                GUICtrlSetData($Button1, "Next")
                $iSavPos = $i;save the current bar-position to $iSavPos
                ExitLoop
            Else
                $iSavPos = 0
                GUICtrlSetData($idProgressbar1, $i)
                Sleep($iWait)
            EndIf
        Next
        If $i > 100 Then
            ;       $iSavPos=0
            GUICtrlSetData($Button1, "Click")
        EndIf

        If GUICtrlSetData($Button1, "Click") Then
            IniWrite($sConfigPath, "Date", "Input1", GUICtrlRead($Input1))
            IniWrite($sConfigPath, "Title", "Input2", GUICtrlRead($Input2))
            IniWrite($sConfigPath, "Edit", "Edit1", GUICtrlRead($Edit1))
        EndIf

        If IniWrite($sConfigPath, "Edit", "Edit1", GUICtrlRead($Edit1)) Then
            GUICtrlSetData($Button1, "Done")
        EndIf
    EndIf
Until $idMsg = $GUI_EVENT_CLOSE



GUICtrlSetData($Input1, IniRead($sConfigPath, "Date", "Input1", "Date"))
GUICtrlSetData($Input2, IniRead($sConfigPath, "Title", "Input2", "Title"))
GUICtrlSetData($Edit1, IniRead($sConfigPath, "Edit", "Edit1", "Start writing..."))



While 1
    $idMsg = GUIGetMsg()

    Switch $idMsg
        Case $GUI_EVENT_CLOSE
            ; Note: Exit needs to be changed to ExitLoop
            ; for any code after the loop to execute.
            ExitLoop
    EndSwitch

    If $idMsg = $GUI_EVENT_CLOSE Then ExitLoop
    If $idMsg = $Button1 Then SendMyData()
WEnd

Func Button1Click()
    IniWrite($sConfigPath, "Date", "Input1", GUICtrlRead($Input1))
    IniWrite($sConfigPath, "Title", "Input2", GUICtrlRead($Input2))
    IniWrite($sConfigPath, "Edit", "Edit1", GUICtrlRead($Edit1))
EndFunc   ;==>Button1Click

IniWrite($sConfigPath, "Date", "Input1", GUICtrlRead($Input1))
IniWrite($sConfigPath, "Title", "Input2", GUICtrlRead($Input2))
IniWrite($sConfigPath, "Edit", "Edit1", GUICtrlRead($Edit1))

Func SendMyData()
    FileDelete('Settings.ini')
    $data = "[General]" & @CRLF & GUICtrlRead($Input2) & @CRLF & @CRLF & GUICtrlRead($Edit1)
    FileWrite('\Settings.ini', $data)
    MsgBox(0, 'Info', 'Data saved')
EndFunc   ;==>SendMyData
#EndRegion ### END Koda GUI section ###
Edited by NeverDUN

Share this post


Link to post
Share on other sites



#2 ·  Posted (edited)

Your program is so simple, progress bars are not necessary. The Do/Until loop is overly complicated. Also, near the end of the program, I see you were deleting the INI file and using FileWrite to write to it. That is very inefficient. I'm posting some simple code that does what you need. Perhaps it can help you see a better way:

#include <ButtonConstants.au3>
#include <EditConstants.au3>
#include <MsgBoxConstants.au3>
#include <GUIConstantsEx.au3>
#include <GuiStatusBar.au3>
#include <ProgressConstants.au3>
#include <WindowsConstants.au3>

Do
    $pass = InputBox("Enter Password", "Please enter the password", "", "*", 150, 120)
    If $pass <> "Password" Then
    EndIf
    If (@error == 1) Then Exit ;
Until $pass == "123"
MsgBox(0, "Success", "Correct password" & @CRLF & "")

Global $sConfigPath = @ScriptDir & "\Settings.ini"

$Form1 = GUICreate("Title", 610, 477, 206, 143)
$Input1 = GUICtrlCreateInput("Date", 480, 16, 113, 21)
$Input2 = GUICtrlCreateInput("Title", 16, 56, 577, 21)
$Edit1 = GUICtrlCreateEdit("", 16, 80, 577, 329)
$Button1 = GUICtrlCreateButton("Save", 520, 424, 75, 25, $BS_DEFPUSHBUTTON)
$StatusBar1 = _GUICtrlStatusBar_Create($Form1)
GUICtrlSetColor(-1, 32250)
GUISetState(@SW_SHOW)

$dateRead = IniRead($sConfigPath, "Date", "Input1", "")
$titleRead = IniRead($sConfigPath, "Title", "Input2", "")
$editRead = IniRead($sConfigPath, "Edit", "Edit1", "")
GUICtrlSetData($Input1, $dateRead)
GUICtrlSetData($Input2, $titleRead)
GUICtrlSetData($Edit1, $editRead)

While 1
    $idMsg = GUIGetMsg()
    Switch $idMsg
        Case $GUI_EVENT_CLOSE
            Exit
        Case $Button1
            If GUICtrlRead($Button1) = "Save" Then
                IniWrite($sConfigPath, "Date", "Input1", GUICtrlRead($Input1))
                IniWrite($sConfigPath, "Title", "Input2", GUICtrlRead($Input2))
                IniWrite($sConfigPath, "Edit", "Edit1", GUICtrlRead($Edit1))
                GUICtrlSetData($Button1, "Done")
            ElseIf GUICtrlRead($Button1) = "Done" Then
                Exit
            EndIf
    EndSwitch
WEnd
Edited by abberration

RAID Calculator | Software Installer

The truth has been suppressed since the dawn of time.

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
Sign in to follow this  
Followers 0

  • Similar Content

    • Skeletor
      By Skeletor
      MS Splash Screens
      The office 2016/17 office suite has made many people turn heads with its functions and especially their splash screen.
      I now present to you, the MS Style Splash Screen. For Rookies, Novices and anyone who wants a ready made splash screen for your gui application.

      You can now download it and also try it out yourself.
      You have three colors to choose from:
      Blue
      Red
      Green
      All three colours are from the famous programs.
      I also included the KODA form to you can have freedom with this splash screen.
      Note: the KODA form does not have the three colours as well as the correct blue. 

      Have fun and enjoy.
      Note:
      I will update the splash to add the automated 3 dots animation at a later stage. 
       
       
    • Skeletor
      By Skeletor
      A gui splash screen. Themed after the famous MS Office Suite.
      Three colours to choose from, Red, Blue and Green.
      You can change the labels to your own application.

      Also bundled with this is the KODA form. So you can open up and see the basic structure of this splash screen.
       
      Splash Screen GUI.zip
    • BlazerV60
      By BlazerV60
      Hello all,
      I've been trying to figure out how to launch Google Chrome in the background (hidden) but it doesn't seem possible. I've tried the following methods:
      ShellExecute("C:\Program Files (x86)\Google\Chrome\Application\chrome.exe", "", "", "", @SW_HIDE) Also I've tried:
      ShellExecute(@ComSpec, "/c start chrome.exe","","",@SW_HIDE) Lastly I tried:
      RunWait('"'&@ProgramFilesDir&'\Google\Chrome\Application\chrome.exe" --silent-launch',@ScriptDir)  
      But all of them launch my chrome browser without hiding it. Does anyone know a workaround for this or if AutoIT just can't Chrome? 
      Bonus points if you know how to make it launch chrome hidden and make it go to https://www.autoitscript.com
       
      Thank you,
      Brian
    • SteveJM
      By SteveJM
      I have a working program currently driven largely through menu selections. I would like to add a toolbar where most of the tollbar button actions are basically the same as menu items, but quicker to access. I have been wading around in toolbar examples, MSDN pages etc, it's clearly going to be a bit of a slog to get everything right, including tooltips etc. I thought I would start with something simple to prove the principle.
      Using bits from the help file examples I have a small program that successfully displays a toolbar. However, what seemed like the most elegant way to deal with the button commands does not seem to work. My understanding was that a toolbar button fires a WM_COMMAND message, with the command Id set by the second parameter in the call to
      _GUICtrlToolbar_AddButton ( $hWnd, $iID, $iImage)
      so I though it would be a good idea to set this Id to the same value as my menu item Id; then it would run the same task which is what I wanted. This did not work. I am using message loop mode and would like to stick with this because some of my scripts run hardware at the same time as the gui; it is easier if I don't have to worry about code being interrupted with the hardware in an unknown state . So I added a handler for WM_COMMAND, with some cribbed display code to try and see why. The toolbar button defintely fired a WM_COMMAND message and the Id looked the same, so no explanation there.
      I guess the issue is with GUIGetMsg() which may be constructed to ignore all but a limited number of control handles, i.e. those made with the GuiCtrlCreate... commands; this is speculation.
      I would dearly love to find a tidy way to get around this. Having some controls handled in the message loop and some in a WM_COMMAND handler, performing the same task, feels ugly. I would be very grateful for further insight from someone experienced with handling a toolbar. Perhaps I should be trying to fire the menu item. I have attached a code snippet to try and illustrate the issue.
       
       
       
      ToolbarTrial.au3
    • XinYoung
      By XinYoung
      Hello all,
      I've been working on 4 standalone scripts. They each have their own GUI and are now independent .exe's. But instead of having 4 separate icons on my computer, is it possible to put them all together into one .exe?
      What I want is one interface with tabs. Each script's GUI would be on their own respective tab. Is this possible?
      The different scripts don't need to communicate with one another. I just want them all in one .exe.
      I can't find this anywhere... Any help would be greatly appreciated. Thank you!