WM_COPYDATA return

[MrCreatoR]

3 minutes ago, Danyfirex said:

compare if they have same value

Yes they are the same, i don't know why i didn't thought about that in the first place.

Thanks.

 

4 minutes ago, Danyfirex said:

maybe I can do it in my dreams meanwhile

It's always good to dream! But soon everything will be better! 🍻

Edited May 17, 2020 by MrCreatoR

[argumentum]

...I'm kind of lost.
The main script sends "_StringRepeat('Send', Random(10, 100))"
The child responds "_StringRepeat('Return', Random(10, 100))"

Where can I read what the main sent to the child in the child ?

[Danyfirex]

Inside _WM_COPYDATA check $tData.Data

 

Saludos

 

[argumentum]

@Danyfirex, this look awesome, very cool.

The _WM_COPYDATA is used as an event, to trigger the read memory.
Is there a way, that is not too far out of your way, to trigger the memory read without using a GUI for it ?, as a memory write that triggers a memory read, or simple in the main loop read, that is not heavy for AutoIt ?

I know this is not the OP question but, can't help to wonder since is all a memory read/write and the GUI is just for the event handler. No GUI dependency would be like, WOW.

Thanks.

Edited May 17, 2020 by argumentum
grammar :)

[Bilgus]

You still need a message loop

Windows doesn't give you one without a GUI

 

Non CLI Autoit apps have an internal window

You could use the internal autoit window

    AutoItWinSetTitle(@ScriptName)
    $hAutoitInternal = WinGetHandle(@ScriptName)

 

[argumentum]

5 minutes ago, Bilgus said:

You still need a message loop

...the script needs a loop, OnEvent or not. So, a loop is not a big deal.

 

6 minutes ago, Bilgus said:

You could use the internal autoit window

actually no. I can not  GUIRegisterMsg() it.

[Bilgus]

nah you need to use SetWindowSubclass

AutoItWinSetTitle(@ScriptName)
$hAutoitInternal = WinGetHandle(@ScriptName)

$hMsgProc = DllCallbackRegister(NewMessage, 'lresult', 'hwnd;uint;wparam;lparam;uint_ptr;dword_ptr')
_WinAPI_SetWindowSubclass($hAutoitInternal, DllCallbackGetPtr($hMsgProc), $iMyID)

Func NewMessage($hWnd, $iMsg, $wParam, $lParam, $iId, $pData)
    #forceref $iID, $pData
    Return _WinAPI_DefSubclassProc($hWnd, $iMsg, $wParam, $lParam)
EndFunc

Func _Exit()
    If $hMsgProc Then
        _WinAPI_RemoveWindowSubclass($hAutoitInternal, DllCallbackGetPtr($hMsgProc), $iMyID)
        DllCallbackFree($g_hMsgProc)
    EndIf

 

Edited May 17, 2020 by Bilgus
Add #forceref $iID, $pData Return _WinAPI_DefSubclassProc($hWnd, $iMsg, $wParam, $lParam)

[argumentum]

1 minute ago, Bilgus said:

nah you need to use SetWindowsSubclass

WOW, thanks. So... , will AutoIt still receive it's messages or am I now in charge of every event ?

[Bilgus]

Quote

...the script needs a loop, OnEvent or not. So, a loop is not a big deal.

When you do your own message loop it has to be pumped in a timely manner so it sometimes becomes a big deal

at least with the subclass you can still have AutoIt take care of the minute 

[Bilgus]

No you just pass on what you don't want to handle to the default with 

_WinAPI_DefSubclassProc()

The helpfile explains it pretty clearly

 

Edited May 17, 2020 by Bilgus

[argumentum]

2 minutes ago, Bilgus said:

When you do your own message loop it has to be pumped in a timely manner so it sometimes becomes a big deal ...

...all this is way above my pay grade !.
I would have to build some coding experience to comfortably code with sub-classing.
Thanks for the coding class  

I'll give a try in one of those moments when I'm bored.
It'll be good to expand my knowing to the point that this technique is in my arsenal   

[Bilgus]

OH don't conflate the two, Subclassing an existing winproc is not doing your own message loop its the same idea as GUIRegister message

doing your own message loop isn't near as simple

Edited May 17, 2020 by Bilgus

[KaFu]

Using COM for IPC and triggering events without a loop but via ObjEvent() could be a good method too.

Edit: Or do something like this in a loop and look for changes / reset the var when read.

 

Edited May 18, 2020 by KaFu

[argumentum]

looks like a solution to my question  
...it does crash running x64  

@trancexx, ..it been about a decade since the code. Can it be fixed ?
..it won't run on v3.3.6.1 or 3.3.8.1 either ( on Win10 ), so maybe there was no solution from the get go, regarding x64.
Not that I "need" to run x64 but your view regarding this is welcomed.

Edit: ..now that I read more about it, this would be an overkill, and misused to fit the purpose of triggering an event. 

Edited May 18, 2020 by argumentum