An initial note. Quite a few of my CRAP buttons use "runas" so I can use an admin account to run things from a non-admin login.

If I use the new "skip command window" option, I have to set the application as runas.exe and pass everything else (the actual program as well as the user account details) to the command as a lengthy parameter.

It works -- of course! -- and is exactly as the command actually works but it means, for me at least, most of my buttons -- those that don't need a results window left open, anyway -- are going to be runas.exe with the actual program I'm running (along with its parameters) demoted to a parameter of runas.

Not sure if this matters or not! I haven't found an error with it, just a change of focus. :)

Here’s my reasoning for the application launch mode. With the command line window the command is all arguments side. If I am going to skip it then I need a reliable way to tell what the executable is without dealing with the arguments side of things.

-hamradio (March 31, 2024, 08:47 AM)

There were, I think, some commands that took a lot of tinkering to make work properly -- and there are definitely some where the command window should be left open as well as some that don't.

I think I made most things work by either using start /b or not -- the remote desktop example I documented in the help is one where it was needed, but -- and I think it's down to Microsoft rather than anything else! -- expecting consistency is possibly a step too far!

I thought I'd left a note on here a few days ago to help with updating the help, if it's needed, for the new version, but I don't see the message so I expect I abandoned it accidentally :)

Anyhoo -- I'm still using CRAP only on a Windows 10 machine, but that doesn't mean I don't have Win11 available to test on if it's useful!

Along with the AHK experts here I would also ask on AHK Forums

-MilesAhead (July 04, 2023, 01:12 PM)

Have done. I thought I'd ask here first -- where everyone is utterly lovely -- in case I was being extremely stupid.  :D

I haven't decided if I will learn V2.x yet. 

I was intuitively sure my code wasn't complex enough to fail to work in either, but it would only compile in v1 so it looks like I have some learning to do too! (I think #NoEnv is now the default so isn't required, and I think v2 didn't like my read loops so I suspect some syntactical changes there too, but at the point of compilation it didn't seem important to acquire v2 compatibility so I didn't bother trying to fix it!)