This automatically launches two instances of a web browser, each with their own process ID. The first step is to create a shortcut that will only need to be run typically once per boot. My approach is to break the process into two steps. But that’s fine since we leave them open all the time anyway. That is to say we can never launch the websites on our own if we want to use the shortcuts.
Here is what I came up with:ġ) There are two things that are guaranteed to be unique between each launched web browser, provided they are executed in their own processes – the process ID and the resulting HWND or Window IDĢ) However since these change on each execution of the process, we need to make Autohotkey the authority for launching these web applications and ensure that each webapp launches in its own process. Thus I had to figure out my own approach. The trouble is, due to how the web sites work, none of the conventional approaches I’ve found for toggling them on and off worked. In this example, I use two websites constantly throughout the day and I constantly have to switch back and forth to them. But what if you can’t use the window title? This post shows you how to toggle between an application where the title constantly changes and you otherwise have nothing consistent about the application with which to configure Autohotkey to use. You can configure it for example to toggle between applications based on their window title. Wouldn’t it be great if you could just press a keyboard shortcut to launch/resume any application? This is where Autohotkey excels. Sure, you can click the application you want on the task bar or use Alt-Tab. But what happens when you have a ton of programs and tabs open? The tasks many only take a few seconds each, but added up over the course of a year or more, it really adds up! One such common task involves switching between applications in Windows. Autohotkey is an invaluable tool for automating tasks we perform hundreds of times per day without even thinking of it.
0 kommentar(er)
