spudw2k

Not a huge fan of creating a new label every time a button is clicked. Seems unnecessary and a recipe for a memory leak. Am I missing something?

I think Dan's recommendation isn't bad, but adds more complexity to account for. I would recommend creating a function/routine for each button case; something like this: case $But_check_1 But1() case $But_check_2 But2() case $But_check_3 But3() case $But_check_4 But4() case $But_check_5 But5() Func But1() ;button 1 code... ;... ;... EndFunc Func But2() ;button 2 code... ;... ;... EndFunc Func But3() ;button 3 code... ;... ;... EndFunc Func But4() ;button 4 code... ;... ;... EndFunc Func But5() ;button 5 code... ;... ;... EndFunc then calling the functions directly in order: But1() But2() But3() But4() But5()

What Melba was trying to convey is you shouldn't have to click each button, but instead run the code that occurs when a button click Msg is detected. I imagine you have some code beneath each case...is that correct? case $But_check_1 ;button 1 code... ;... ;... case $But_check_2 ;button 2 code... ;... ;... case $But_check_3 ;button 3 code... ;... ;... case $But_check_4 ;button 4 code... ;... ;... case $But_check_5 ;button 5 code... ;... ;...

It's been a while, but I used to do an export of my wells transactions to a csv. If that feature/function is still possible it might make your QuickBooks balancing task a little easier and keep your wellsfargo online activity safe.

Sounds like a bad idea. That timeout is there for a reason. Especially considering the nature of it--being an actively logged in financial account--why would you want to keep it from timing out if you are not using it?

Are you saying you would like a pop-up preview of the image if you hover over the label which contains an image path? You can probably use the SplashImageOn function, combined with some code to detect if the control is being hovered over.

These threads and UDF may help. https://www.autoitscript.com/forum/index.php?showtopic=196833 I have had success using it to interact with .NET controls.

Is the goal to suppress your popup if the user does any activity, or specific key presses or mouse clicks? One idea that comes to mind is just check idle time. _WinAPI_GetIdleTime()

Thank you for posting some example code. It is not jumping out at my why the _SQL_CLOSE error would be occurring, but the message is saying the variable $sqlConn isn't declared before it is being sent to the the _SQL_CLOSE function. For the $CmdLine error, sounds like no command line parameters are being sent to the script/exe. If your script relies on command line parameters to work, and none are provided, you should probably add some error checking. For example: ;if your script is expecting four cmd line paramters to work, verify that four params were provided before executing the script If $CmdLine[0] <> 4 Then Exit ;Also a good idea to add additional error checking that the 4 parameters are expected values Regarding getting help with the _sql.au3 and MailSlot.au3 UDFs, the authors, if they are still active members on the forums, would be the best contacts.

Welcome @Cypharr. Unfortunately it is against the forum rules to discuss, "Launching, automation or script interaction with games or game servers, regardless of the game."; so I am afraid you won't get assistance with this script. Please also note rule #7 in the forum rules as well, as this post will likely be locked.

Ok, well that is a good sign. The handle does seems a little short to me (thinking x86 versus x64). Are the subscripts and the GUI script all using the same architecture x86/x64? I'm pretty sure you will need to use the _GUICtrlListBox functions, as using GUICtrlSetData uses the control ID instead of the handle...but you mentioned you already tried that. What return value do you get from the _GUICtrlListBox_AddString function?

Try ListBox1 as the last parameter in the ControlGetHandle function, then check the variable to verify a handle was obtained.

As mentioned in the article, unquoted uninstall paths are a fairly low risk/security concern--compared to unquoted service paths--as uninstallers typically involve user initiation and rights escalation. Still, not a terrible suggestion to address in the next release/beta.

Looks like GetTempPath looks for the %TMP% variable first. If you update %TMP%, the @TempDir macro updates. _PrintTempVars("----------Environment vars at script start----------") EnvSet("Temp", "C:\temp") EnvSet("Tmp", "C:\tmp") _PrintTempVars("----------Environment vars after update----------") Func _PrintTempVars($sTitle = "") $sTempMacro = @TempDir $sTempEnv = EnvGet("Temp") ConsoleWrite($sTitle & @CRLF & "Env:" & $sTempEnv & @CRLF & "@TempDir:" & $sTempMacro & @CRLF & @CRLF) EndFunc or if you delete the %TMP% environment variable, GetTempPath/@TempDir will use %TEMP% EnvSet("Temp", "C:\temp") EnvSet("Tmp")

^ Agreed. If operating in a domain environment, you can set permissions to allow the computer account (COMPUTER$) to have permissions to the folder, and avoid storing user credentials; either explicitly, or a using security group (*preferred).