![]() $dimensions = -join ($png.Width, " x ", $png.Height) $watcher.Path = "$HOME\AppData\Local\Packages\_cw5n1h2txyewy\TempState\ScreenClip" In my example, I have it stored at D:\Apps\Windows Powershell Scripts\ScreenSnip Manager\Activate.ps1Ĭontent of the script $watcher = New-Object System.IO.FileSystemWatcher Next, create a file "Activate.ps1" somewhere. optionally clear out the ScreenClip folder. ![]() rename/copy to desired userspace folder.monitor the folder for the new files appearing there.All files are dumped to the same system directory ScreenClip, which as of Win10 21H1 is located at C:\Users\Your-username\AppData\Local\Packages\_cw5n1h2txyewy\TempState\ScreenClip. Step 2: Powershell scriptįoreword: Windows does create 3 files after the Snip - Screenshot, its Thumbnail (always 364x180 on my FullHD setup) and a Json file. Note: The path to the script must be valid and must contain the file hereby named "Activate.ps1". In short, the argument instructs the Powershell to load the lines of our script as one line and then execute it, thus going around the usual Windows restrictions regarding launching standalone scripts. Command "Get-Content -Path 'D:\Apps\Windows Powershell Scripts\ScreenSnip Manager\Activate.ps1' -Raw | Invoke-Expression" ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |