-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keeping quick access window setup #17
Comments
Probably use the window handle or ProcessID? Use titles seems a bit too ambiguous. |
I think the handle will change? Not sure about processID |
I think window handle only change when we close the window and open new one. I remember when I used Switcheroo, I used a similar number to save to a txt file, not ProcessID, probably window handle. |
Yeah the handle will change once the window is closed. Probably we can save it, but that won't be permanent. Process name may work, but not work for multiple keyword pointing to multiple window with the same process. |
Personally I prefer we do window handle for now, seems much simpler, long term maybe we can try to do something clever like "activate" the background processes (like processes in notification area but not in taskbar) |
Seems this problem we need to be clear about 2 cases, first is |
Yep, processID will change i tested way back. Dont remember if i tried window handle, if the window is closed, we can consider it not needed any more and the window handle can be disgarded. |
keeping the quick access window setup saved to settings would be nice, so when flow restarts they can be continually used. The ones that are no longer found can then be removed.
Don't know if there is a unique identifier that can be used to save, otherwise maybe the window title like how it's done now.
The text was updated successfully, but these errors were encountered: