Leaderboard

So maybe i just haven't been looking hard enough, but i could not find how to make toast notifications in win8+ from AutoIt. I looked at it on and off, and finally made some progress. Github repository: https://github.com/genius257/au3toast Zip download: https://github.com/genius257/au3toast/archive/52f6eb0c5e6543777e19010a6c64f46e4dbe8fe0.zip I am still working on event support, but would like some feedback from the forum so far Thanks!

Thank you My guess is the combination of attributes used, but haven't spend much time on the XML, after i got it somewhat usable Glad to hear! Yeah in general AutoIt has been missing proper native toasts since the windows 8 overhaul, as far as i know Yeah it's a little rough around the edges currently, but i am working towards providing a good implementation little by little Happy to hear it will be used

Oh this is nice. How did you get them to persist like that? EDIT: I've only spent about 10 minutes playing around with this, but I love it. AutoIt has really needed this because there hasn't been a solution yet for Windows 11 that has been able to have the toasts persist in the notification center like this. Fantastic work. I look forward to watching this progress over time. I definitely can make great use of this.

PEGetImportsX86.au3

..what are the options: run in same process or span another process. Make faster small updates or make longer taking jump from color to color. I would span another process as the rainbow feature is independent of the main script. IPC seems like OMG !. About this IPC: #include <GUIConstantsEx.au3> Exit main() Func main() If StringInStr($CmdLineRaw, "/rainbowThing") Then Return rainbow() Opt("GUIOnEventMode", 1) GUICreate(@ScriptName & " - main", 300, 200) GUISetOnEvent($GUI_EVENT_CLOSE, "SpecialEvents") GUICtrlCreateButton(" stop the other process ", 10, 10) GUICtrlSetOnEvent(-1, main_BttnStop) GUICtrlCreateInput(" something from the other process ", 10, 40, 280) GUISetState() ShellExecute(@AutoItExe, '"' & @ScriptFullPath & '" /rainbowThing') While Sleep(300) WEnd EndFunc ;==>main Func main_BttnStop() ConsoleWrite('+ Func main_BttnStop()' & @CRLF) WinClose(@ScriptName & " - rainbow") EndFunc ;==>main_BttnStop Func SpecialEvents() Switch @GUI_CtrlId Case $GUI_EVENT_CLOSE ControlSetText(@ScriptName & " - main", "", "[CLASS:Edit; INSTANCE:1]", "good bye world @" & @HOUR & ":" & @MIN & ":" & @SEC & "." & @MSEC) GUIDelete() Exit EndSwitch EndFunc ;==>SpecialEvents Func rainbow() Opt("GUIOnEventMode", 1) GUICreate(@ScriptName & " - rainbow", 300, 100) GUISetOnEvent($GUI_EVENT_CLOSE, "SpecialEvents") Local $idBttn = GUICtrlCreateButton(" my rainbow process ", 10, 10) ;~ GUISetState() ; or not. Is not needed While Sleep(300) GUICtrlSetData($idBttn, @HOUR & ":" & @MIN & ":" & @SEC & "." & @MSEC) WEnd EndFunc ;==>rainbow it does Interprocess communication via something else but the use is the same. You'll do fancy IPC when you get more experience

You mentioned _WD_Navigate not working, but this function doesn't appear in your code. Please explain. Also, you should show us the console output to allow better understanding of the issue.

Parsix, This is not an "example" so it had been moved from the "WebDriver Examples" thread. M23

My pleasure Just a couple of extra tidbits I've found while having a play... Those base scroll unit values can be found in $__g_aSB_WindowInfo. So you don't want to re-calculate - first do a _GUIScrollBars_Init(), then just cycle through the array until you find your window handle. $__g_aSB_WindowInfo[$iIndex][0] = $hWnd $__g_aSB_WindowInfo[$iIndex][2] = $iHScrollUnit $__g_aSB_WindowInfo[$iIndex][3] = $iVScrollUnit The other thing I found was that the _WinAPI_GetClientWidth() and _WinAPI_GetClientHeight() values will change depending on if you're displaying a scroll bar. This is a good thing. If the vertical bar is showing, the overall width will shrink accordingly to accommodate whatever real estate was lost. But the take away is: make sure the the vertical/horizontal bars are in the correct visibility state before you take your measurements. Hope that makes sense!

Thanks everyone for replying. Yes, I too did more analysis as Jos wanted more crash details. WER showed error with MSVCP140.dll. I installed newest distributable of MV C++ x64. Crash still occurred. I installed newest distributable of MS C++ x86. No more crash. Apparently there is a prereq for new version of Scrite 5.5.x of C++. Maybe this should be documented on the download pages. Follow up question for jos: Is there any problem continuing to use Scrite v4.4.6 (that came with autoit 3.3.16) with new autoit 3.3.18 if I use the newer au3.keywords.properties that came with autoit 3.3.18. If no problem, should I also use the new api\au3.api that came with autoit 3.3.18 or use the older api\au3.api that came with 3.3.16? Thanks

It's no problem. I'm starting to fall behind with street lingo myself. Kids these days with their "sigmas" and "mewing" and such

Can't tell, as you haven't provided any details of the crash. People have reported crashes before, which mostly were resolved by removing/installing that latest version of some dll's This is the answer from ChatGPT: So please provide the details on the crash to see if somebody else has reported that already and fixed it.

AutoIt v3.3.18.0 has been released - mainly a UDF release. Thanks to @jpm and the MVPs who were responsible for the majority of code in this version. Download it here. Complete list of changes: History

I installed new AutoIT release 3.3.18. I'm on Windows 10 x64 with latest patches. I do not have VSC. When I run the Scite.exe included with the AutoIT 3.3.18 installer It opens, but when I click on any menu item or try to type it hangs then crashes. What is really strange is that task manager shows when running Scite that the scite.exe is listed and also a child process Windows cmd Console. This is now how the Scite.exe included with 3.3.16 worked. I'm concerned that the new Schite.exe is malware. I reviewed the Scite.exe in the 3.3.17.0 and 3.3.17.1 betas and see that is when this newer scite.exe began being included with autoit installer. I saw on forum that in February 2025 a new beta rewrite of scrite.exe was released incorporating VSC, I installed that beta and it too fails. Scite.exe version numbers: with autoit 3.3.18 v5.5.6, with autoit betats3.3.17.x v5.5.6, and with scrite beta (on forum) v 5.5.5. So asking developers: 1, Why does scite v5.5.6 included with autoit 3.3.18 crash? 2. Does the scite v5.5.5 and 5.5.6 contain malware considering it odd it opens a Windows command console as a child process under scrite.exe? 3. If scite v5.5.6 is good and it's just my system doesn't meet requirements (such as VSC) what are the requirements and should you provide a version in installer for my system type? 4 In all cases, how do users who install portable version (which I normally do though for testing above I used the installer) get around this problem? Thanks