Easy-to-manage touch screens
무료 오픈소스 터치스크린으로 USB 설정 가이드, 드래그‑드롭 편집기, 로컬 제어를 제공하며 Home Assistant용으로 제작되었습니다
Portable Windows cursor scheme manager: preview all 17 roles, apply in one click, import a folder or .zip.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A portable app for changing the Windows cursor: a library of schemes in the app's folder, and a
graphical client that previews each scheme in all 17 roles before you apply it.
Double-click CursorSelector.exe.
A native .NET Framework executable: no installer, no administrator rights, no external
dependencies and no PowerShell. It can be pinned to the taskbar or to the Start menu.
Every subfolder of Library\ is a scheme. Put the .cur / .ani files in it and that is all:
The app matches the files to the Windows roles on its own, in this order:README 전문 보기 ↗Download and details: protagonistlabs.app/cursorselector
A portable app for changing the Windows cursor: a library of schemes in
%APPDATA%\ProtagonistLabs\Cursor Selector\, and a
graphical client that previews each scheme in all 17 roles before you apply it.
Double-click CursorSelector.exe.
A native .NET Framework executable: no installer, no administrator rights, no external dependencies and no PowerShell. It can be pinned to the taskbar or to the Start menu.
Every subfolder of Library\ is a scheme. Put the .cur / .ani files in it and that is all:
Library\
Windows_11_dark\
pointer.cur
busy.ani
...
My pack\
Normal Select.cur
...
The app matches the files to the Windows roles on its own, in this order:
scheme.json in the folder, if there is one: manual control, takes priorityInstall.inf in the folder, if the pack ships one: the author's official mappingNormal Select, pointer, dgn1,
Diagonal Resize 1, VertRes, busy, link, handwriting and so on)Files in the root of the folder take priority; subfolders are searched only if the root is empty (otherwise a "bonus cursors" subfolder would steal roles from the main set).
scheme.json: when you want to correct the mapping{
"name": "The name shown in the list",
"cursors": {
"Arrow": "pointer.cur",
"Wait": "busy.ani",
"Hand": "link.cur"
}
}
Roles you leave out stay unmapped. The role names are the ones in the Windows registry:
Arrow, Help, AppStarting, Wait, Crosshair, IBeam, NWPen, No, SizeNS, SizeWE, SizeNWSE, SizeNESW, SizeAll, UpArrow, Hand, Pin, Person.
Ctrl+F; Down moves into the list, Esc clears it). The schemes from
Library\ come first; a single heading marks where the ones already registered in Windows begin
(Windows' own themes and packs installed through an .inf). Right-click a scheme to show its files
or to remove it from the library — removal goes to the Recycle Bin, and only for folders in
Library\..ani cursors animate.
Roles with no file appear dimmed, with —, and go back to the Windows default if you apply the
scheme. Each cursor sits on a mid-grey chip: it is the only shade on which both black cursors
(Capitaine, VS Cursors) and white ones (Windows Inverted) can be seen; on white or on black some of
them would disappear. Click a tile to see that cursor at 128px with its file name, size and frame
count.HKCU\Control Panel\Cursors, notifies the system
(SPI_SETCURSORS) and registers the scheme, so it also shows up in Windows' Mouse Properties.
The effect is immediate, with no restart and no sign-out..zip or any file in the folder of an unpacked pack
(.cur, .ani, Install.inf); dragging and dropping a folder or a .zip anywhere on the window
does the same. The pack is copied into Library\ (unpacked, without the wrapper folder from the
archive), selected and applied on the spot, so the download can be deleted afterwards. A name that
already exists in the library is reused, not overwritten.ACTIVE pill in the list, and applying or restoring is
confirmed for three seconds in the status line at the bottom right.The app's interface is in English. Everything can be reached from the keyboard: arrows to move
through the list, Tab between buttons, Space or Enter to press, with a visible focus ring.
The interface follows the Protagonist Labs visual identity, with the same tokens as the sites:
ground #0a0d13, accent #4c8dff, three steps of text (#e8eef6 / #8a97aa /
#5d6879). In the studio's branding note the panels and edges are white with alpha, so they sit
the same over any background; here they are composited into opaque colours, because WinForms
draws opaque controls and has no compositing layer under them.fonts\, embedded by build.cmd, OFL — licences beside them):
on a machine where none of them is installed, the app used to fall back to Segoe UI and looked
like any other WinForms program. A copy installed on the machine still wins over the embedded one.
They are registered twice at startup, once for GDI+ and once for GDI, because TextRenderer draws
through the second one and ignores fonts registered only with the first.letter-spacing, so the labels are drawn character by character.#06101f text and a coloured halo;
the ghost one with an edge-bright border over panel.20), rounded corners (33) and border colour (34, in
0x00BBGGRR, not the order of the palette hex).Two things from the note can not be applied here:
| File | Role |
|---|---|
CursorSelector.exe | the application |
Library\ | the library of schemes, one subfolder per scheme; in %APPDATA%\ProtagonistLabs\Cursor Selector\ since 1.4.0 (a Library\ beside the exe, from older versions or the with-cursors zip, moves there at start) |
backup.json | the cursor configuration from before the first apply; written only once; in the same AppData folder |
whatsnew.txt | the What's new notes, embedded in the executable at build time |
src\CursorSelector.cs | the source code |
build.cmd | rebuilds the executable |
app.ico | the icon, embedded in the executable at build time |
fonts\ | the brand's typefaces (OFL), embedded in the executable at build time, with their licences |
Deleting a folder from Library\ removes the scheme from the list. If that scheme was the one
applied, Windows falls back to the default cursors for the missing files: use Restore saved
cursors or apply another scheme.
After changes in src\CursorSelector.cs:
build.cmd
It uses the C# compiler in %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\, which ships with
Windows, so no SDK needs installing.
The source is plain ASCII: the special characters in the interface (—, ·, …) are written as
\uXXXX escapes. That way it does not depend on a BOM and does not break if you open it in an
editor that strips one.