added comments to readme (#12)

Reviewed-on: #12 Co-authored-by: Aleksandr Neychev <alexnejchev73@gmail.com>
2026-08-15 02:56:58 +00:00
parent 9c6ec489e1
commit 743974a0c1
2 changed files with 18 additions and 0 deletions
@@ -172,6 +172,15 @@ always in the same place, so it is known where to look — and the look must com
 it, since a popup set small and quiet for the middle of a text goes unnoticed in the
 corner of a monitor.

+Some applications those are is decided by what a window exposes rather than by
+what it is written in. A Win32 control creates a system caret and is read at once;
+Chromium and Electron draw their own and report it over the accessibility
+interfaces. A window that paints its text into a bare canvas has nothing to report
+at all — and both kinds live in the same application: the editors of a JetBrains
+IDE answer, since the runtime keeps a caret for them, while a tool window whose
+interface is painted by Compose holds no text component for UI Automation or the
+Java Access Bridge to find. That window is where the fixed point earns its keep.
+
 Which mode the look belongs to is explained in a tooltip next to the mode itself
 rather than by a line of text in the section: the sliders below show other numbers
 after a switch of the mode, and that is a question asked once.