What is "synchronous mode" considered for AutoIT?

[Zein]

Reading the documentation for a function, I found this line:
"The _WinAPI_ReadDirectoryChanges() function works only in synchronous mode."

What exactly is considered synchronous and asynchronous modes for AutoIt? I've tried to google it and search the forums, but the words are never brought up. 

Does anyone have a place I can learn more of this mode?

Thanks. 

[Jos]

you are sure you read my posts in that specific thread?

... And why not ask it there?

Jos

[junkew]

http://msdn.microsoft.com/query/dev10.query?appId=Dev10IDEF1&l=EN-US&k=k(ReadDirectoryChangesW);k(DevLang-C);k(TargetOS-WINDOWS)&rd=true

Search google for synchronous and asynchronous calls.

[Zein]

Just now, junkew said:

http://msdn.microsoft.com/query/dev10.query?appId=Dev10IDEF1&l=EN-US&k=k(ReadDirectoryChangesW);k(DevLang-C);k(TargetOS-WINDOWS)&rd=true

Search google for synchronous and asynchronous calls.

So synchronous and asynchronous apply to autoit as it would any language?

So would AutoIt always be synchronous? Or is there some other deciding factor here?

1 minute ago, Jos said:

you are sure you read my posts in that specific thread?

... And why not ask it there?

Jos

I felt it was a fundamentally different thread, where he was asking for help. You also seemed done with that specific thread.

[Jos]

13 minutes ago, Zein said:

I felt it was a fundamentally different thread, where he was asking for help.

Not really as I've mentioned it there in relation to the issue posted, but the OP seems to be totally ignoring it, hence my last comment.

13 minutes ago, Zein said:

You also seemed done with that specific thread.

So yes, but merely with the OP, not when somebody shows effort and has a valid question.

Jos 

EDIT: I do have the working version of that script, as proposed, ready when that OP is up to speed as to why things don't work. 

Edited November 15, 2018 by Jos

[junkew]

Read multithreading in faq.

See register callback in helpfile

So in general AutoIt is synchronous calls of functions.

[Zein]

4 hours ago, junkew said:

Read multithreading in faq.

See register callback in helpfile

So in general AutoIt is synchronous calls of functions.

Thank you, I was unaware of any multithreading in AutoIT.
 

17 hours ago, Jos said:

Not really as I've mentioned it there in relation to the issue posted, but the OP seems to be totally ignoring it, hence my last comment.

So yes, but merely with the OP, not when somebody shows effort and has a valid question.

Jos 

EDIT: I do have the working version of that script, as proposed, ready when that OP is up to speed as to why things don't work. 

Oh that makes sense, sorry for the bad assumption I made :(. I plan on using the function call on a lab computer so that I can make a really roundabout/simplistic "remote shell" like program. It should be running at all times like a service, but I can't entirely figure out how to make the script exit if I ever need it to without committing another change to the directory.

 

[BrewManNH]

There is a way to run that WinAPI function asynchronously, but I think it's way over the head of the poster in that thread. It's over mine I know.

[Zein]

Definitely over mine too then. 

[Zein]

@Jos

I'm working with the little code snippet you provided in the other thread as a base, and I'm curious about behavior.

Why does a single file change (heck, I only change 1 letter in a text file then save) cause 2 iterations of the while loop?
I thought that ReadDirectoryChanges would block until the next file change, but it seems to return twice back to back before blocking again. 

I changed it to detect only Last_Write:
$aData = _WinAPI_ReadDirectoryChanges($hDirectory, $FILE_NOTIFY_CHANGE_LAST_WRITE, $pBuffer, 50000, 1)

But can't seem to make it iterate once per change. 

[Jos]

I don't know and haven't looked into the details for that windows call. 

Just for the record, this is in my mind to most simple version of using a GUI and subprocess. They subprocess will end when the gui ends. 

expandcollapse popup

; created by Jos - AutoIt forums
#NoTrayIcon
#include <APIFilesConstants.au3>
#include <EditConstants.au3>
#include <FileConstants.au3>
#include <GUIConstantsEx.au3>
#include <MsgBoxConstants.au3>
#include <WindowsConstants.au3>
#include <WinAPIError.au3>
#include <WinAPIFiles.au3>
; define folder to monitor..
Global $g_sPath = @DesktopDir & '\Changing folder'
; ----------------------------------------------------------------------------------------
; check for /FileMon_feeder which means it is the subprocess which will monitor the folder
For $x = 1 To $CMDLINE[0]
    Global $T_Var = StringLower($CMDLINE[$x])
    Global $aData
    Global $curcontent = ""
    Select
        Case $T_Var = "/FileMon_feeder"
            ; get main PID from commandline and monitor that.
            Global $H_Cmp = $CMDLINE[$x + 1]
            If Not FileExists($g_sPath) Then
                MsgBox(BitOR($MB_ICONERROR, $MB_SYSTEMMODAL), 'Error', "Folder doesn't exists:" & $g_sPath)
                Exit
            EndIf
            Global $pBuffer = _WinAPI_CreateBuffer(8388608)
            Global $hDirectory = _WinAPI_CreateFileEx($g_sPath, $OPEN_EXISTING, $FILE_LIST_DIRECTORY, $FILE_SHARE_ANY, $FILE_FLAG_BACKUP_SEMANTICS)
            If @error Then
                _WinAPI_ShowLastError('', 1)
            EndIf            ; Run while main script exists.
            While ProcessExists($H_Cmp)
                ConsoleWrite(" Wait for changes..")
                $aData = _WinAPI_ReadDirectoryChanges($hDirectory, BitOR($FILE_NOTIFY_CHANGE_FILE_NAME, $FILE_NOTIFY_CHANGE_DIR_NAME, $FILE_NOTIFY_CHANGE_ATTRIBUTES, $FILE_NOTIFY_CHANGE_SIZE, $FILE_NOTIFY_CHANGE_LAST_WRITE, $FILE_NOTIFY_CHANGE_LAST_ACCESS, $FILE_NOTIFY_CHANGE_CREATION, $FILE_NOTIFY_CHANGE_SECURITY), $pBuffer, 8388608, 1)
                ConsoleWrite(" Something changed?")
                If Not @error And IsArray($aData) Then
                    $curcontent = ControlGetText("Show Folder change", "", "Edit1")
                    For $x = 1 To $aData[0][0]
                        $curcontent &= $aData[$x][0] & " -> " & $aData[$x][1] & @CRLF
                    Next
                    ControlSetText("Show Folder change", "", "Edit1", $curcontent)
                Else
                    _WinAPI_ShowLastError('', 1)
                EndIf
            WEnd
            Sleep(500)
            Exit
    EndSelect
Next
; start this script again to monitor the folder
Global $pid = Run('"' & @AutoItExe & '" "' & @ScriptFullPath & '" /FileMon_feeder ' & @AutoItPID)
;----------------------------------------------------
; Show the GUI
$Form1 = GUICreate("Show Folder change", 493, 263)
$Edit1 = GUICtrlCreateEdit("", 16, 24, 457, 193, BitOR($ES_MULTILINE, $ES_AUTOVSCROLL, $WS_VSCROLL))
GUISetState(@SW_SHOW, $Form1)
While 1
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            ; close subprocess monitoring the folder
            ProcessClose($pid)
            Exit
    EndSwitch
WEnd

Jos

[Zein]

I was considering a similar approach, albeit more primitive. 

For now I'll be looking into the multiple returns. 

[Jos]

This one is actually quite primitive. I would prefer using a mailslot and only add what is new instead of replacing the whole text each time.

Jos

 

[Zein]

A mailslot? I've never heard that term before. 

[Jos]

It creates a "pipe" for communication between applications. Check the details : 

 

Jos