Idea
Add a Windows Explorer context-menu entry ("Encrypt with ZeeCrypt" / "Decrypt with ZeeCrypt") for files and folders, so users don't have to open the app and drag files in manually.
Why now
The MSI installer (dist/windows/installer.wxs) already writes to the registry for the .pcv file association (Software\Classes\ZeeCrypt.pcv\...). A shell context-menu entry is the same kind of registry work — a shell key under Software\Classes\*\shell\ZeeCryptEncrypt (and/or Directory\shell\... for folders) pointing at the exe with the dropped path as an argument.
Open questions to resolve before implementing
Scope
Registry-only change to dist/windows/installer.wxs; shouldn't require app code changes if %1 argument handling already works as expected above.
Idea
Add a Windows Explorer context-menu entry ("Encrypt with ZeeCrypt" / "Decrypt with ZeeCrypt") for files and folders, so users don't have to open the app and drag files in manually.
Why now
The MSI installer (
dist/windows/installer.wxs) already writes to the registry for the.pcvfile association (Software\Classes\ZeeCrypt.pcv\...). A shell context-menu entry is the same kind of registry work — ashellkey underSoftware\Classes\*\shell\ZeeCryptEncrypt(and/orDirectory\shell\...for folders) pointing at the exe with the dropped path as an argument.Open questions to resolve before implementing
ZeeCrypt.execurrently support being launched with a file path as a command-line argument to auto-populate the drop target? (Checkflagusage insrc/ZeeCrypt.go— the file association'sshell\open\commandalready does"ZeeCrypt.exe" "%1", so there's likely existing support here, but confirm it also handles being launched with no prior UI state expected, and multiple files at once for multi-select.)HKCU\Software\Classes) to match the installer's existing no-admin-required, per-user scopeimages/lock.ico)Scope
Registry-only change to
dist/windows/installer.wxs; shouldn't require app code changes if%1argument handling already works as expected above.