added administrator grant

CursorLang/CursorLang.csproj

@@ -6,6 +6,7 @@
         <Nullable>enable</Nullable>
         <ImplicitUsings>enable</ImplicitUsings>
         <UseWPF>true</UseWPF>
+        <ApplicationManifest>app.manifest</ApplicationManifest>
     </PropertyGroup>
 
     <ItemGroup>

CursorLang/app.manifest

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="utf-8"?>
+<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
+  <assemblyIdentity version="1.0.0.0" name="CursorLang.app" />
+
+  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
+    <security>
+      <requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
+        <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
+      </requestedPrivileges>
+    </security>
+  </trustInfo>
+
+  <application xmlns="urn:schemas-microsoft-com:asm.v3">
+    <windowsSettings>
+      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
+    </windowsSettings>
+  </application>
+</assembly>

README.md

@@ -1,3 +1,10 @@
 # cursor-lang
 
-The WPF application displays the keyboard layout at the cursor
+The WPF application displays the keyboard layout at the cursor
+
+The app requests administrator rights on startup. Windows does not deliver
+keyboard input to a low-level hook while an app of a higher integrity level
+holds the focus, so without elevation the Caps Lock hotkey would silently stop
+working in Task Manager, Registry Editor and anything else started as
+administrator. Note that a plain shortcut in the startup folder cannot launch an
+elevated app — use a Task Scheduler task with the "highest privileges" flag.