Anomolies with V1 to V2 Conversion
Posted: 17 Sep 2023, 16:38
Been using V1 for over a decade for stand-alone controllers and or providing interface glue for an application that has no cli
Started by working on one of these systems ... it has 3 AHK scripts that run concurrently
1) glue app watches for content in an import folder ... content triggers the process of importing the file and then archiving the file ... a busy flag is checked and or set to ensure this process doesn't bump into other ahk processes
2) monitor that starts and keeps apps running ... this process periodically tests to see if apps exist ... if not they are restarted and minimized
3) Monitors network devices (sends email notifications for missing/restored devices)
Anomaly one - open/active apps|folders on the desktop are randomly minimizing ... the minimize statements in AHK explicitly spell out Window Titles so not following why "ACTIVE" unrelated Windows are being minimized
Anomaly two - the 3rd AHK script appears to be treated differently in that it is identified as an Application by Task Manager showing both on the taskbar as well as in the hidden icons ... expectation is that all AHK scripts be running in the background in the hidden icon section of the taskbar
Started by working on one of these systems ... it has 3 AHK scripts that run concurrently
1) glue app watches for content in an import folder ... content triggers the process of importing the file and then archiving the file ... a busy flag is checked and or set to ensure this process doesn't bump into other ahk processes
2) monitor that starts and keeps apps running ... this process periodically tests to see if apps exist ... if not they are restarted and minimized
3) Monitors network devices (sends email notifications for missing/restored devices)
Anomaly one - open/active apps|folders on the desktop are randomly minimizing ... the minimize statements in AHK explicitly spell out Window Titles so not following why "ACTIVE" unrelated Windows are being minimized
Anomaly two - the 3rd AHK script appears to be treated differently in that it is identified as an Application by Task Manager showing both on the taskbar as well as in the hidden icons ... expectation is that all AHK scripts be running in the background in the hidden icon section of the taskbar