OnEvent when something shows up in a ListBox

[PhoenixXL]

GUIRegisterMsg($WM_COMMAND, "WM_COMMAND")

GUIRegisterMsg($WM_CLOSE, "WM_CLOSE")

You should give a try to WM_COPYDATA, if you read Msdn, its for the purpose you are searching for

[CountyIT]

Back to the speak English. EXACTLY what advice are you giving me? You keep responding it riddles!

[PhoenixXL]

Check Guinness's signature for WM_COPYDATA example...

Edit : here is the link

Edited April 19, 2013 by PhoenixXL

[CountyIT]

Thanks for trying PhoenixXL. I went back and tried to convert those two tiny scripts and move to WM_COPYDATA and am just so totally lost on the WM_COPYDATA that I give up.

[BrewManNH]

Seeing as how you've gotten the text to show up in Script 2's listbox, perhaps this script could be modified to your needs to let you know when the text in the listbox has changed, specifically the part where the script is using WM_COMMAND and monitoring the EN_CHANGE message to see if something has changed.

[CountyIT]

I don't know if you want to step in the middlw of this one or not. I have already been chastised for not using WM_COPYDATA It is kind of interesting though. I have a GUI on the main program that is hidden because there is really no user interaction with it. My intent was to send commands to it via SendMessage() to more or less control the program remotely. The two functions I (use to) register were:

GUIRegisterMsg($WM_CLOSE, "WM_CLOSE")

GUIRegisterMsg($WM_COMMAND, "WM_COMMAND")

and what I would do from the second script was:

_SendMessage($WindowHandle, $WM_CLOSE, 0, 0)

_SendMessage($WindowHandle, $WM_COMMAND, 0, 0)

The _SendMessage($WindowHandle, $WM_CLOSE, 0, 0) worked without fail. The correct function on the first script ("WM_COLSE") executed. The _SendMessage($WindowHandle, $WM_COMMAND, 0, 0) would not work. The function on the first script never executed. I tried several other commands in place of WM_COMMAND and nada.

Finally, in a drunk stupor, I thought I would try something a little closer to WM_CLOSE in the list of commands in WindowsConstants.gui so I choose WM_ENABLE. It worked. I got away from it at that point. I figure either certain commands can't be sent with _SendMessage() or certain commands can't be registered with GUIRegisterMsg(). Don't know but WM_ENABLE seemed to work where many other did not...

[BrewManNH]

You stated that you were able to update the text in the listbox, the code I pointed you to (although it's using an input control) will read that the input control has been changed and reacts to that change with the $WM_COMMAND function, and then further reacts to that change by looking at the EN_CHANGE message.

That script would work with the GUI that has your listbox, so all you have to do is update the text in the listbox, watch for any messages from that listbox using WM_COMMAND, and then doing something if that message is a E_CHANGE message. All of this is done in the script that creates the GUI with the listbox.