Passing more than two 32-bit ints via WM_APP (WM_USER)

[Spiff59]

I'm looking for the most efficient way to pass three 32-bit integer values between two compiled and running scripts.

Anything involving disk access or registry changes would be my last resort. An environment varaible is a possibility, but not a thrilling one. ControlSend() may be another option, but one of the scripts won't have a GUI and I doubt this method is particularily efficient either.

I've been looking at creating a user-defined message (WM_USER) using _WinAPI_RegisterWindowMessage(), but I don't know if there's a way to get past the limit of only passing two 32-bit integers via the wParam and iParam parameters?

Is there a way to sneak a little more data into a windows message call?

Can one pass an address or handle to some data created in script A to script B, and once script B receives the address it can attach to it and reference the data?

Edited August 1, 2010 by Spiff59

[Richard Robertson]

http://msdn.microsoft.com/en-us/library/ms692727%28VS.85%29.aspx

Use this function to allocate space 3 ints long (12 bytes) and pass the pointer as one of your params.

[SmOke_N]

http://msdn.microsoft.com/en-us/library/ms692727%28VS.85%29.aspx

Use this function to allocate space 3 ints long (12 bytes) and pass the pointer as one of your params.

Ha!, I like that idea.

I might consider ( for simplicity ) using WM_COPYDATA though. Pass as a string and convert on either side.