Feature request: machine "installable"

[teknowledgist]

I like this project. Thanks for bringing it out of the AHK forums to a more public space.

I'd like to make this available as a Chocolatey package. The only sticking point is that packages are supposed to be "machine installs", and, currently, the WinPos.txt location is always the same as the AHK script. The recommended location for non-installed Chocolatey packages in in the Chocolatey\lib\<packagename> subfolder of %ProgramData%, but that is not writable by non-admins. The bigger problem is that there is only one WinPos.txt for the entire system regardless of the location.

I'd like to get this script using the per-user %AppData% location for the capture. It should probably check the script location first to allow for portable users and backward compatibility, but if there is no WinPos.txt in the script directory and/or the user doesn't have modify rights to it (un-elevated), then it should use something like %AppData%\DockWin\WinPos.txt.

If I ever get time to grok AHK, I'm happy to submit a PR, but I thought I'd throw this out there for anyone with more time/skill to poke at.

(Addendum: A major upgrade would be to allow multiple "sets" of Windows for each user.)

[rwese]

Sounds like a good idea, and I also like it to be usable by multiple users on the same machine.

Changing the WinPos.txt to be stored elsewhere, and maybe under a more suiting name, isn't such a big issue, for the sake of simplicity and portability I just left is as is.

I have not used Chocolatey before so I might not be of much help there.

(Addendum: explain what a "set" of Windows would be please)

[teknowledgist]

I can take care of making the Chocolatey package. 😊 Sent from my phone. Please excuse the brevity.

…

On Sep 22, 2017, at 12:11 PM, René ***@***.***> wrote: Sounds like a good idea, and I also like it to be usable by multiple users on the same machine. Changing the WinPos.txt to be stored elsewhere, and maybe under a more suiting name, isn't such a big issue, for the sake of simplicity and portability I just left is as is. I have not used Chocolatey before so I might not be of much help there. (Addendum: explain what a "set" of Windows would be please) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[teknowledgist]

By "sets" of windows, I meant being able to "Capture Screens" with several different configurations. So, maybe a user have two monitors in one office and one large one in another. He/She has a different "set" of window locations/sizes for each monitor. Maybe also, they have a "work" arrangement and a "play" arrangement.

The "Restore Screens" menu item could either ask which "set" to use (I guess capturing would require a naming option.) or have a submenu.