I use AutoIt for control.
In order to perform a number of functions with AutoIt, I have a WinForms application that includes AutoIt, and this grabs the Windows handle of WealthLab.
A usage example is to ensure WealthLab is set to the foreground. The Winforms code is below:
The windows handle name includes the WealthLab build number, which of course increments.
I was hoping that it might be possible for this handle name to not include the build number so that my control application that runs AutoIt does not need to be in step with Wealthlab releases.
In order to perform a number of functions with AutoIt, I have a WinForms application that includes AutoIt, and this grabs the Windows handle of WealthLab.
A usage example is to ensure WealthLab is set to the foreground. The Winforms code is below:
CODE:
private const string WlpMainName = "Wealth-Lab 7 Build 40"; public bool Focus() { var handle = NativeMethods.FindHandle(WlpMainName); if (handle == IntPtr.Zero) return false; return NativeMethods.SetForeGroundWindow(handle); }
The windows handle name includes the WealthLab build number, which of course increments.
I was hoping that it might be possible for this handle name to not include the build number so that my control application that runs AutoIt does not need to be in step with Wealthlab releases.
Rename
Why not use the AutoItSetOption function using the WinTitleMatchMode option?
https://www.autoitscript.com/autoit3/docs/intro/windowsadvanced.htm
https://www.autoitscript.com/autoit3/docs/intro/windowsadvanced.htm
QUOTE:
I was hoping that it might be possible for this handle name to not include the build number
In my opinion, the benefit of recognizing the build number by everyone (including the less tech savvy users) checking if their program version is actual outweighs not having it there. 🤷
AutoItSetOption works great. Thanks for the pointer
Your Response
Post
Edit Post
Login is required